Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: markus.t.metzger@intel.com, gdb-patches@sourceware.org,
	       markus.t.metzger@gmail.com
Subject: Re: [rfc 6/8] record disas: omit function names by default
Date: Fri, 15 Feb 2013 18:33:00 -0000	[thread overview]
Message-ID: <20130215183256.GA16845@host2.jankratochvil.net> (raw)
In-Reply-To: <831uchtp4y.fsf@gnu.org>

On Fri, 15 Feb 2013 19:20:45 +0100, Eli Zaretskii wrote:
> > record backtrace:
> > Print function names from which instruction in the execution log ran.
> 
> Isn't that just a backtrace?  If so, I suggest
> 
>   Print a backtrace starting at the function to which the instruction
>   in the log belongs.

That's the problem, the name "backtrace" itself is already a bit confusing.

It is a "backtrace" into history, not into upper frames.
	(gdb) record backtrace 
	_IO_vsnprintf
	_IO_vfprintf_internal
	strchrnul
	_IO_vfprintf_internal
	__GI__IO_default_xsputn
You can see _IO_vfprintf_internal called strchrnul which then returned back to
_IO_vfprintf_internal.  This is not a real "backtrace".

I was already considering renaming the command as the term is a bit overloaded
in the debugger context.

Maybe "record list-functions"?  It is also very similar to the "record list"
command there which lists lines:
      (gdb) btrace list 24-34
      24     in stdio_file_flush () at ../../../git/gdb/ui-file.c:525-529
      25     in ui_file_data () at ../../../git/gdb/ui-file.c:175-180
      26     in stdio_file_flush () at ../../../git/gdb/ui-file.c:522-523
      27     in gdb_flush () at ../../../git/gdb/ui-file.c:185

While I understand "record list" was trying to match the existing "list"
command I do not find it too intuitive, so maybe "record list-lines"?


Thanks,
Jan


  reply	other threads:[~2013-02-15 18:33 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 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: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 [this message]
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
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: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:31 ` [rfc 3/8] record-full.h: rename record_ into record_full_ markus.t.metzger
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=20130215183256.GA16845@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