This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RE: [rfc 6/8] record disas: omit function names by default
> -----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