From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org, markus.t.metzger@gmail.com,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: [patch v9 18/23] record: add "record function-call-history" command
Date: Tue, 05 Mar 2013 20:12:00 -0000 [thread overview]
Message-ID: <20130305201153.GR2386@host2.jankratochvil.net> (raw)
In-Reply-To: <1362416770-19750-19-git-send-email-markus.t.metzger@intel.com>
On Mon, 04 Mar 2013 18:06:05 +0100, Markus Metzger wrote:
> Add command to print the function names from recorded instructions.
>
> The command supports iterating over the execution log similar to the "list"
> command.
>
> This command provides a quick high-level overview over the recorded execution
> log at function granularity without having to reverse-step.
>
> CC: Eli Zaretskii <eliz@gnu.org>
>
> 2013-03-04 Markus Metzger <markus.t.metzger@intel.com>
>
> * target.c (target_call_history, target_call_history_from,
> target_call_history_range): New.
> * target.h (target_ops) <to_call_history, to_call_history_from,
> to_call_history_range>: New fields.
> (target_call_history, target_call_history_from,
> target_call_history_range): New declaration.
> * record.c (get_call_history_modifiers, cmd_record_call_history,
> record_call_history_size): New.
> (_initialize_record): Add the "record function-call-history" command.
> Add "set/show record function-call-history-size" commands.
> * record.h (record_print_flag): New.
[...]
> --- a/gdb/record.c
> +++ b/gdb/record.c
[...]
> +/* The "record function-call-history" command. */
> +
> +static void
> +cmd_record_call_history (char *arg, int from_tty)
> +{
> + int flags, size;
> +
> + require_record_target ();
> +
> + flags = get_call_history_modifiers (&arg);
> + size = (int) record_call_history_size;
> + if (size < 0)
> + size = INT_MAX;
Again please comment, I do not understand off-hand what is the goal of this
code.
> +
> + if (arg == NULL || *arg == 0 || strcmp (arg, "+") == 0)
> + target_call_history (size, flags);
> + else if (strcmp (arg, "-") == 0)
> + target_call_history (- size, flags);
Just '-size', no space there.
> + else
> + {
> + ULONGEST begin, end;
> +
> + begin = get_insn_number (&arg);
> +
> + if (*arg == ',')
> + {
> + arg = skip_spaces (++arg);
> +
> + if (*arg == '+')
> + {
> + arg += 1;
> + size = get_context_size (&arg);
> +
> + no_chunk (arg);
> +
> + target_call_history_from (begin, size, flags);
> + }
> + else if (*arg == '-')
> + {
> + arg += 1;
> + size = get_context_size (&arg);
> +
> + no_chunk (arg);
> +
> + target_call_history_from (begin, -size, flags);
> + }
> + else
> + {
> + end = get_insn_number (&arg);
> +
> + no_chunk (arg);
> +
> + target_call_history_range (begin, end, flags);
> + }
> + }
> + else
> + {
> + no_chunk (arg);
> +
> + target_call_history_from (begin, size, flags);
> + }
> +
> + dont_repeat ();
> + }
> +}
[...]
> --- a/gdb/target.h
> +++ b/gdb/target.h
> @@ -908,6 +908,16 @@ struct target_ops
> /* Disassemble a section of the recorded execution trace. */
> void (*to_insn_history_range) (ULONGEST begin, ULONGEST end, int flags);
>
> + /* Print a function trace of the recorded execution trace. */
> + void (*to_call_history) (int size, int flags);
Please comment the rules which range will be printed depending on SIZE.
> +
> + /* Print a function trace of the recorded execution trace starting
> + at instruction FROM. */
> + void (*to_call_history_from) (ULONGEST begin, int size, int flags);
Please comment the meaning/relationship of BEGIN and SIZE.
> +
> + /* Print a function trace of an execution trace section. */
Comment whether END is inclusive or exclusive.
> + void (*to_call_history_range) (ULONGEST begin, ULONGEST end, int flags);
> +
> int to_magic;
> /* Need sub-structure for target machine related rather than comm related?
> */
> @@ -2003,4 +2013,13 @@ extern void target_insn_history_from (ULONGEST from, int size, int flags);
> /* See to_insn_history_range. */
> extern void target_insn_history_range (ULONGEST begin, ULONGEST end, int flags);
>
> +/* See to_call_history. */
> +extern void target_call_history (int size, int flags);
> +
> +/* See to_call_history_from. */
> +extern void target_call_history_from (ULONGEST begin, int size, int flags);
> +
> +/* See to_call_history_range. */
> +extern void target_call_history_range (ULONGEST begin, ULONGEST end, int flags);
> +
> #endif /* !defined (TARGET_H) */
> --
> 1.7.1
OK with the comments.
Thanks,
Jan
next prev parent reply other threads:[~2013-03-05 20:12 UTC|newest]
Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 17:07 [patch v9 00/23] branch tracing support for Atom Markus Metzger
2013-03-04 17:07 ` [patch v9 16/23] record: default target methods Markus Metzger
2013-03-05 20:10 ` Jan Kratochvil
2013-03-04 17:07 ` [patch v9 01/23] thread, btrace: add generic branch trace support Markus Metzger
2013-03-05 20:06 ` Jan Kratochvil
2013-03-05 22:02 ` Tom Tromey
2013-03-06 21:11 ` Doug Evans
2013-03-07 7:50 ` Metzger, Markus T
2013-03-07 22:57 ` Doug Evans
2013-03-04 17:07 ` [patch v9 03/23] linux, i386, amd64: enable btrace for 32bit and 64bit linux native Markus Metzger
2013-03-05 20:06 ` Jan Kratochvil
2013-03-04 17:07 ` [patch v9 08/23] gdbserver, linux, btrace: add btrace support for linux-low Markus Metzger
2013-03-05 20:09 ` Jan Kratochvil
2013-03-06 9:17 ` Metzger, Markus T
2013-03-06 13:33 ` Jan Kratochvil
2013-03-04 17:07 ` [patch v9 05/23] remote, btrace: add branch trace remote ops Markus Metzger
2013-03-05 20:07 ` Jan Kratochvil
2013-03-06 9:00 ` Metzger, Markus T
2013-03-04 17:07 ` [patch v9 04/23] xml, btrace: define btrace xml document style Markus Metzger
2013-03-05 20:07 ` Jan Kratochvil
2013-03-04 17:07 ` [patch v9 02/23] linux, btrace: perf_event based branch tracing Markus Metzger
2013-03-05 20:06 ` Jan Kratochvil
2013-03-06 10:11 ` Mark Kettenis
2013-03-06 10:29 ` Metzger, Markus T
2013-03-04 17:07 ` [patch v9 10/23] remote, btrace: add branch tracing protocol to Qbtrace packet Markus Metzger
2013-03-05 20:09 ` Jan Kratochvil
2013-03-06 9:19 ` Metzger, Markus T
2013-03-04 17:07 ` [patch v9 07/23] gdbserver, btrace: add generic btrace support Markus Metzger
2013-03-05 20:08 ` Jan Kratochvil
2013-03-06 9:15 ` Metzger, Markus T
2013-03-06 13:22 ` Jan Kratochvil
2013-03-04 17:08 ` [patch v9 20/23] record-btrace, disas: omit pc prefix Markus Metzger
2013-03-05 20:13 ` Jan Kratochvil
2013-03-04 17:08 ` [patch v9 09/23] btrace, x86: disable on some processors Markus Metzger
2013-03-05 20:09 ` Jan Kratochvil
2013-03-04 17:08 ` [patch v9 19/23] record, btrace: add record-btrace target Markus Metzger
2013-03-05 20:13 ` Jan Kratochvil
2013-03-06 9:57 ` Metzger, Markus T
2013-03-06 13:35 ` Jan Kratochvil
2013-03-06 14:01 ` Metzger, Markus T
2013-03-06 16:28 ` Jan Kratochvil
2013-03-04 17:08 ` [patch v9 11/23] target: add add_deprecated_target_alias Markus Metzger
2013-03-05 20:09 ` Jan Kratochvil
2013-03-04 17:08 ` [patch v9 06/23] btrace, doc: document remote serial protocol Markus Metzger
2013-03-04 18:08 ` Eli Zaretskii
2013-03-05 20:08 ` Jan Kratochvil
2013-03-06 9:06 ` Metzger, Markus T
2013-03-06 9:50 ` Jan Kratochvil
2013-03-06 10:01 ` Metzger, Markus T
2013-03-06 12:07 ` Jan Kratochvil
2013-03-06 12:13 ` Metzger, Markus T
2013-03-06 12:17 ` Jan Kratochvil
2013-03-04 17:08 ` [patch v9 22/23] testsuite, gdb.btrace: add btrace tests Markus Metzger
2013-03-04 19:47 ` Jan Kratochvil
2013-03-05 6:39 ` Metzger, Markus T
2013-03-05 20:14 ` Jan Kratochvil
2013-03-06 15:32 ` christian.himpel
2013-03-06 16:35 ` Jan Kratochvil
2013-03-04 17:09 ` [patch v9 23/23] btrace, remote: drop qbtrace packet Markus Metzger
2013-03-04 18:15 ` Eli Zaretskii
2013-03-05 20:15 ` Jan Kratochvil
2013-03-04 17:09 ` [patch v9 18/23] record: add "record function-call-history" command Markus Metzger
2013-03-04 18:07 ` Eli Zaretskii
2013-03-05 20:12 ` Jan Kratochvil [this message]
2013-03-04 17:09 ` [patch v9 21/23] doc, record: document record changes Markus Metzger
2013-03-04 18:13 ` Eli Zaretskii
2013-03-05 20:13 ` Jan Kratochvil
2013-03-04 17:09 ` [patch v9 15/23] record-full.h: rename record_ into record_full_ Markus Metzger
2013-03-05 20:10 ` Jan Kratochvil
2013-03-04 17:09 ` [patch v9 13/23] record: make it build again Markus Metzger
2013-03-05 20:10 ` Jan Kratochvil
2013-03-04 17:09 ` [patch v9 14/23] record-full.c: rename record_ in record_full_ Markus Metzger
2013-03-05 20:10 ` Jan Kratochvil
2013-03-04 17:09 ` [patch v9 17/23] record: add "record instruction-history" command Markus Metzger
2013-03-04 18:14 ` Eli Zaretskii
2013-03-05 20:11 ` Jan Kratochvil
2013-03-04 17:10 ` [patch v9 12/23] record: split record Markus Metzger
2013-03-05 20:09 ` Jan Kratochvil
2013-03-06 12:43 ` Crash of GDB with gdbserver btrace enabled [Re: [patch v9 00/23] branch tracing support for Atom] Jan Kratochvil
2013-03-06 14:40 ` Metzger, Markus T
2013-03-06 15:31 ` Metzger, Markus T
2013-03-06 17:06 ` Jan Kratochvil
2013-03-06 18:08 ` Metzger, Markus T
2013-03-07 9:06 ` Jan Kratochvil
2013-03-07 9:41 ` Metzger, Markus T
2013-03-07 10:00 ` Metzger, Markus T
2013-03-07 10:14 ` Jan Kratochvil
2013-03-07 10:33 ` Metzger, Markus T
2013-03-07 12:07 ` Jan Kratochvil
2013-03-07 12:33 ` Metzger, Markus T
2013-03-07 14:45 ` Jan Kratochvil
2013-03-07 15:22 ` Metzger, Markus T
2013-03-07 15:46 ` Jan Kratochvil
2013-03-07 15:12 ` Pedro Alves
2013-03-07 15:33 ` Metzger, Markus T
2013-03-07 15:39 ` Jan Kratochvil
2013-03-07 15:41 ` Pedro Alves
[not found] ` <20130318170643.GA15625@host2.jankratochvil.net>
[not found] ` <514758DA.2060905@redhat.com>
2013-03-20 15:52 ` [commit] [patch] Code cleanup: Remove parameter quitting [Re: Crash of GDB with gdbserver btrace enabled] Jan Kratochvil
[not found] ` <20130318192604.GA2786@host2.jankratochvil.net>
[not found] ` <51477828.30000@redhat.com>
2013-03-26 0:15 ` Jan Kratochvil
2013-04-03 18:05 ` Pedro Alves
2013-03-07 10:08 ` Crash of GDB with gdbserver btrace enabled [Re: [patch v9 00/23] branch tracing support for Atom] Jan Kratochvil
2013-03-06 15:41 ` Jan Kratochvil
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=20130305201153.GR2386@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@gmail.com \
--cc=markus.t.metzger@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