From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: markus.t.metzger@intel.com
Cc: palves@redhat.com, tromey@redhat.com, kettenis@gnu.org,
gdb-patches@sourceware.org, markus.t.metzger@gmail.com
Subject: Re: [patch v6 02/12] cli, btrace: add btrace cli
Date: Mon, 17 Dec 2012 18:32:00 -0000 [thread overview]
Message-ID: <20121217183214.GA14232@host2.jankratochvil.net> (raw)
In-Reply-To: <1355760101-26237-3-git-send-email-markus.t.metzger@intel.com>
On Mon, 17 Dec 2012 17:01:31 +0100, markus.t.metzger@intel.com wrote:
[...]
> --- a/gdb/btrace.c
> +++ b/gdb/btrace.c
[...]
> @@ -166,3 +188,581 @@ next_btrace (struct thread_info *tp)
>
> return VEC_index (btrace_block_s, btp->btrace, btp->iterator);
> }
> +
> +/* Enable branch tracing. Turn errors into warnings. */
> +
> +static void
> +warn_enable_btrace (struct thread_info *tp)
> +{
> + volatile struct gdb_exception error;
> +
> + TRY_CATCH (error, RETURN_MASK_ERROR)
> + enable_btrace (tp);
> +
> + if (error.message != NULL)
> + warning (_("%s"), error.message);
"%s" does not need localization.
> +}
> +
> +/* Disable branch tracing. Turn errors into warnings. */
> +
> +static void
> +warn_disable_btrace (struct thread_info *tp)
> +{
> + volatile struct gdb_exception error;
> +
> + TRY_CATCH (error, RETURN_MASK_ERROR)
> + disable_btrace (tp);
> +
> + if (error.message != NULL)
> + warning (_("%s"), error.message);
"%s" does not need localization.
> +}
[...]
> +static void
> +cmd_btrace_disable (char *args, int from_tty)
> +{
> + struct thread_info *tp;
> +
> + if (args != NULL && *args != 0)
> + {
> + ALL_THREADS (tp)
> + if (number_is_in_list (args, tp->num))
> + warn_enable_btrace (tp);
Here should be warn_disable_btrace.
> + }
> + else
> + {
> + tp = find_thread_ptid (inferior_ptid);
> + if (tp == NULL)
> + error (_("Couldn't disable branch tracing: no inferior thread."));
> +
> + disable_btrace (tp);
> + }
> +}
[...]
> +static void
> +do_btrace_list_function (struct btrace_block *trace)
> +{
> + struct minimal_symbol *msymbol;
> + struct symbol *symbol;
> + const char* func;
GDB is using 'const char *' style.
> +
> + func = "??";
> + symbol = find_pc_function (trace->begin);
> + if (symbol != NULL)
> + func = SYMBOL_PRINT_NAME (symbol);
[...]
> +static void
> +do_btrace_list_item (struct btrace_block *trace, enum btrace_list_flags flags)
> +{
> + if (flags & BTR_LIST_ADDRESS)
if ((flags & BTR_LIST_ADDRESS) != 0)
> + do_btrace_list_address (trace);
> +
> + if (flags & BTR_LIST_FUNCTION)
dtto
> + do_btrace_list_function (trace);
> +
> + if (flags & BTR_LIST_LINE)
dtto
> + do_btrace_list_line (trace);
> +}
[...]
> +/* The "btrace list" command. */
> +
> +static void
> +cmd_btrace_list (char *args, int from_tty)
[...]
> + if (flags & BTR_LIST_TOTAL)
if ((flags & BTR_LIST_TOTAL) != 0)
> + {
[...]
> +/* Print the disassembly of a btrace block. */
> +
> +static void
> +do_btrace (struct btrace_block *trace, int flags)
> +{
> + struct gdbarch *gdbarch = target_gdbarch ();
> +
> + if (trace == NULL)
> + error (_("No trace."));
> +
> + if (trace->end < trace->begin)
> + warning (_("Bad trace: %s - %s"), paddress (gdbarch, trace->begin),
> + paddress (gdbarch, trace->end));
Shouldn't this be rather gdb_assert? How to create such case?
> +
> + gdb_disassembly (gdbarch, current_uiout, 0, flags, -1,
> + trace->begin, trace->end + 1);
> +}
[...]
No need for a repost wrt the changes above.
Thanks,
Jan
next prev parent reply other threads:[~2012-12-17 18:32 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 16:02 [patch v6 00/12] branch tracing support for Atom markus.t.metzger
2012-12-17 16:02 ` [patch v6 09/12] gdbserver, linux, btrace: add btrace support for linux-low markus.t.metzger
2012-12-17 16:02 ` [patch v6 02/12] cli, btrace: add btrace cli markus.t.metzger
2012-12-17 18:32 ` Jan Kratochvil [this message]
2012-12-18 7:36 ` Metzger, Markus T
2012-12-18 8:35 ` Jan Kratochvil
2012-12-18 9:04 ` Jan Kratochvil
2012-12-18 9:11 ` Metzger, Markus T
2012-12-17 16:02 ` [patch v6 06/12] remote, btrace: add branch trace remote ops markus.t.metzger
2012-12-17 19:57 ` Jan Kratochvil
2012-12-17 16:02 ` [patch v6 12/12] btrace, x86: disable on some processors markus.t.metzger
2012-12-17 17:11 ` Mark Kettenis
2012-12-19 16:13 ` Metzger, Markus T
2012-12-19 16:36 ` Mark Kettenis
2012-12-21 10:38 ` Jan Kratochvil
2012-12-17 17:37 ` H.J. Lu
2012-12-19 15:58 ` Metzger, Markus T
2012-12-17 20:35 ` Jan Kratochvil
2012-12-17 16:02 ` [patch v6 08/12] gdbserver, btrace: add generic btrace support markus.t.metzger
2012-12-17 20:43 ` Jan Kratochvil
2012-12-17 16:02 ` [patch v6 01/12] thread, btrace: add generic branch trace support markus.t.metzger
2012-12-17 16:03 ` [patch v6 04/12] linux, i386, amd64: enable btrace for 32bit and 64bit linux native markus.t.metzger
2012-12-17 16:03 ` [patch v6 10/12] test, btrace: add branch tracing tests markus.t.metzger
2012-12-17 20:26 ` Jan Kratochvil
2012-12-17 16:03 ` [patch v6 05/12] xml, btrace: define btrace xml document style markus.t.metzger
2012-12-17 19:53 ` Jan Kratochvil
2012-12-18 7:43 ` Metzger, Markus T
2012-12-17 16:03 ` [patch v6 03/12] linux, btrace: perf_event based branch tracing markus.t.metzger
2012-12-17 16:03 ` [patch v6 07/12] btrace, doc: document remote serial protocol markus.t.metzger
2012-12-17 16:03 ` [patch v6 11/12] test, btrace: more branch tracing tests markus.t.metzger
2012-12-17 18:45 ` [patch v6 00/12] branch tracing support for Atom Jan Kratochvil
2012-12-17 19:34 ` Tom Tromey
2012-12-18 7:24 ` Metzger, Markus T
2012-12-18 9:20 ` Jan Kratochvil
2012-12-18 10:14 ` Metzger, Markus T
2012-12-18 13:55 ` Jan Kratochvil
2012-12-19 9:59 ` Metzger, Markus T
2012-12-19 12:13 ` Mark Kettenis
2012-12-19 12:37 ` Jan Kratochvil
2012-12-20 7:17 ` Jan Kratochvil
2012-12-20 9:14 ` Metzger, Markus T
2012-12-20 11:43 ` Jan Kratochvil
2012-12-20 15:20 ` Metzger, Markus T
2012-12-21 19:12 ` Jan Kratochvil
2012-12-22 13:08 ` Jan Kratochvil
2013-01-01 16:35 ` 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=20121217183214.GA14232@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kettenis@gnu.org \
--cc=markus.t.metzger@gmail.com \
--cc=markus.t.metzger@intel.com \
--cc=palves@redhat.com \
--cc=tromey@redhat.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