From: Yao Qi <qiyaoltc@gmail.com>
To: Tim Wiederhake <tim.wiederhake@intel.com>
Cc: gdb-patches@sourceware.org, markus.t.metzger@intel.com,
brobecker@adacore.com
Subject: Re: [PATCH v2 7/8] Python: Move and rename gdb.BtraceFunction
Date: Fri, 21 Apr 2017 16:41:00 -0000 [thread overview]
Message-ID: <86mvb9zs3n.fsf@gmail.com> (raw)
In-Reply-To: <1492771786-26372-8-git-send-email-tim.wiederhake@intel.com> (Tim Wiederhake's message of "Fri, 21 Apr 2017 12:49:45 +0200")
Tim Wiederhake <tim.wiederhake@intel.com> writes:
> Remove gdb.BtraceFunctionCall and replace by gdb.FunctionSegment. Additionally,
> rename prev_segment and next_segment to prev and next.
>
> 2017-04-21 Tim Wiederhake <tim.wiederhake@intel.com>
>
> gdb/ChangeLog:
> * python/py-record-btrace.c (BTPY_REQUIRE_VALID_CALL, btpy_call_type):
> Remove.
> (btrace_func_from_recpy_func): New function.
> (btpy_call_new, btpy_number, btpy_hash, btpy_richcompare): Remove.
> (btpy_call_level, btpy_call_symbol, btpy_call_instructions,
> btpy_call_up, btpy_call_prev_sibling, btpy_call_next_sibling): Rename to ...
> (recpy_bt_func_level, recpy_bt_func_symbol, recpy_bt_func_instructions,
> recpy_bt_func_up, recpy_bt_func_prev, recpy_bt_func_next): This.
> Also, use new helper functions.
> (btpy_list_item): Use new helper functions.
> (recpy_bt_function_call_history): Use new type name.
> (btpy_call_getset): Remove.
> (gdbpy_initialize_btrace): Remove code to initialize
> gdb.BtraceFunctionCall.
> * python/py-record-btrace.h (recpy_bt_func_number, recpy_btb_func_level,
> recpy_btb_func_symbol, recpy_bt_func_instructions, recpy_bt_func_up,
> recpy_bt_func_prev, recpy_bt_func_next): New export.
> * python/py-record.c (recpy_func_type): New static object.
> (recpy_func_new, recpy_func_level, recpy_func_symbol,
> recpy_func_instructions, recpy_func_up, recpy_func_prev,
> recpy_func_next): New function.
> (recpy_element_hash, recpy_element_richcompare): Updated comment.
> (recpy_func_getset): New static object.
> (gdbpy_initialize_record): Add code to initialize gdb.RecordInstruction.
> * python/py-record.h (recpy_func_type, recpy_func_new): New export.
>
> gdb/doc/ChangeLog:
> * python.texi (Recording in Python): Replace gdb.BtraceFunction with
> gdb.RecordFunctionSegment. Rename prev_sibling and next_sibling to
> prev and next.
>
> gdb/testsuite/ChangeLog:
> * gdb.python/py-record-btrace.exp: Rename prev_sibling and next_sibling
> to prev and next.
LGTM.
--
Yao (齐尧)
next prev parent reply other threads:[~2017-04-21 16:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 10:50 [PATCH v2 0/8] Python bindings for GDB record Tim Wiederhake
2017-04-21 10:50 ` [PATCH v2 7/8] Python: Move and rename gdb.BtraceFunction Tim Wiederhake
2017-04-21 12:22 ` Eli Zaretskii
2017-04-21 16:41 ` Yao Qi [this message]
2017-04-21 10:50 ` [PATCH v2 4/8] Python: Remove ptid from gdb.Record interface Tim Wiederhake
2017-04-21 12:20 ` Eli Zaretskii
2017-04-21 10:50 ` [PATCH v2 8/8] Python: Introduce gdb.Instruction class Tim Wiederhake
2017-04-21 12:19 ` Eli Zaretskii
2017-04-24 5:34 ` Wiederhake, Tim
2017-04-21 18:10 ` Yao Qi
2017-04-21 10:50 ` [PATCH v2 1/8] Python: Fix indentation in py-record-btrace.c Tim Wiederhake
2017-04-21 10:50 ` [PATCH v2 3/8] Python: Use correct ptid in btrace recording Tim Wiederhake
2017-04-21 14:49 ` Yao Qi
2017-04-21 10:50 ` [PATCH v2 6/8] Python: Move and rename gdb.BtraceInstruction Tim Wiederhake
2017-04-21 12:23 ` Eli Zaretskii
2017-04-21 15:21 ` Yao Qi
2017-04-21 10:50 ` [PATCH v2 5/8] Python: Introduce gdb.RecordGap class Tim Wiederhake
2017-04-21 12:25 ` Eli Zaretskii
2017-04-21 14:50 ` Yao Qi
2017-04-21 10:50 ` [PATCH v2 2/8] Python: Fix exception handling in py-record-btrace.c Tim Wiederhake
2017-04-21 18:08 ` Yao Qi
2017-04-27 16:35 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86mvb9zs3n.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--cc=tim.wiederhake@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox