Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>,
	Eli Zaretskii <eliz@gnu.org>,
	"Tom Tromey (tromey@redhat.com)" <tromey@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"markus.t.metzger@gmail.com" <markus.t.metzger@gmail.com>
Subject: RE: [rfc 6/8] record disas: omit function names by default
Date: Tue, 19 Feb 2013 08:34:00 -0000	[thread overview]
Message-ID: <A78C989F6D9628469189715575E55B2307B822B5@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <20130218151353.GA14121@host2.jankratochvil.net>

> -----Original Message-----
> From: Jan Kratochvil [mailto:jan.kratochvil@redhat.com]
> Sent: Monday, February 18, 2013 4:14 PM


> On Mon, 18 Feb 2013 15:50:50 +0100, Metzger, Markus T wrote:
> > This goes beyond what "btrace" did and has the potential for lots of discussions -
> > especially when considering optimized code.
> 
> GDB currently has many issues with optimized code where it could behave better
> (even for watchpoints etc.).  It is enough when the feature is useful
> for "-O0 -g" code.
> 
> > It might be better if we postponed it in favor of reverse-stepping,
> 
> OK, fine with that, so that neither "btrace list" nor "record list" will
> exist, in the favor of "reverse-step".

OK, so I keep it on my todo-list but postpone it.


Let's try to close on the command names. Here's what the commands are
supposed to do:

> The idea of those three new commands is to provide a quick overview of the
> execution history at different levels of granularity. Each of those commands
> allows iteration similar to the "list" command. The different levels of granularity
> are:

... instructions (disassembly), source lines, and functions

I'm listing the proposals that were made in this thread. In the end, it's your call
since I need you to approve the patch series. I also trust that you have a better
understanding of GDB's command language than I do.

Markus:
> >   record disassemble ......... instructions
> >   record list ....................... source lines
> >   record backtrace ............. functions

Jan:
> I still find "record list-functions" and "record list-instructions" more clear
> than "record backtrace" and "record disassemble".  Particularly as there is
> the "list" word.
> 
> Sorry for "bikeshedding" it, additionally so late, I do not want to keep this
> discussion longer anymore.

Eli:
> > Maybe "record list-functions"?
> 
> How about "record trace-functions"?

Eli:
>    record instruction-history
>    record source-lines-history
>    record function-call-history

Tom:
> Jan> Maybe "record list-functions"?
> 
> "record history" or "record function-history"?

Thanks,
Markus.
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052


  reply	other threads:[~2013-02-19  8:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 16:31 [rfc 0/8] refactor record markus.t.metzger
2013-02-14 16:30 ` [rfc 7/8] record: add "record backtrace" command markus.t.metzger
2013-02-14 16:30 ` [rfc 6/8] record disas: omit function names by default markus.t.metzger
2013-02-15 16:11   ` Jan Kratochvil
2013-02-15 18:21     ` Eli Zaretskii
2013-02-15 18:33       ` Jan Kratochvil
2013-02-15 19:05         ` Eli Zaretskii
2013-02-15 19:10           ` Jan Kratochvil
2013-02-18  9:43             ` Metzger, Markus T
2013-02-18 13:03               ` Jan Kratochvil
2013-02-18 13:30                 ` Metzger, Markus T
2013-02-18 14:13                   ` Jan Kratochvil
2013-02-18 14:51                     ` Metzger, Markus T
2013-02-18 15:54                       ` Jan Kratochvil
2013-02-19  8:34                         ` Metzger, Markus T [this message]
2013-02-19  8:52                           ` [RFC on command names] " Jan Kratochvil
2013-02-18 16:17               ` Eli Zaretskii
2013-02-15 20:43         ` Tom Tromey
2013-02-14 16:30 ` [rfc 8/8] record: add "record list" command markus.t.metzger
2013-02-14 16:30 ` [rfc 5/8] record: add "record disassemble" command markus.t.metzger
2013-02-14 16:30 ` [rfc 4/8] record: default target methods markus.t.metzger
2013-02-14 16:31 ` [rfc 3/8] record-full.h: rename record_ into record_full_ markus.t.metzger
2013-02-14 16:31 ` [rfc 2/8] record-full.c: rename record_ in record_full_ markus.t.metzger
2013-02-15  8:45   ` Jan Kratochvil
2013-02-14 16:32 ` [rfc 1/8] record: make it build again markus.t.metzger
2013-02-15 11:18 ` [rfc 0/8] refactor record Metzger, Markus T
2013-02-15 16:15 ` 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=A78C989F6D9628469189715575E55B2307B822B5@IRSMSX102.ger.corp.intel.com \
    --to=markus.t.metzger@intel.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=markus.t.metzger@gmail.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