From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Cc: brobecker@adacore.com, tromey@redhat.com, teawater@gmail.com
Subject: Re: [RFA] print error message if (auto) disassembly failed
Date: Fri, 17 Apr 2009 10:05:00 -0000 [thread overview]
Message-ID: <83myafk338.fsf@gnu.org> (raw)
In-Reply-To: <83prfbk50b.fsf@gnu.org>
> Date: Fri, 17 Apr 2009 12:23:48 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: tromey@redhat.com, teawater@gmail.com, gdb-patches@sourceware.org
>
> > Date: Thu, 16 Apr 2009 16:59:44 -0700
> > From: Joel Brobecker <brobecker@adacore.com>
> > Cc: gdb-patches@sourceware.org
> >
> > > The default is "auto", which means:
> > >
> > > If AUTO (which is the default), or there's no line info to determine
> > > the source line of the next instruction, display disassembly of next
> > > instruction instead. */
> > >
> > > But I agree with you that this is the wrong default.
> > > I think the default should be "off".
> >
> > Would anyone object to changing the default to "off"?
>
> My vote is to set it to "off", since this is additional functionality
> that evidently not everyone likes.
Btw, the documentation of "auto" is misleading: it makes it sound like
it should _always_ display the disassembly of the next instruction.
But in fact, it only does so when you step over code that doesn't have
line info information or whose source file is unavailable. So how
about the following patch? (If it is accepted, I will fix the manual
as well.)
2009-04-17 Eli Zaretskii <eliz@gnu.org>
* stack.c (_initialize_stack) <disassemble-next-line>: Doc fix.
--- gdb/stack.c~ 2009-04-02 04:05:29.000000000 +0300
+++ gdb/stack.c 2009-04-17 13:00:05.940500000 +0300
@@ -2145,13 +2145,16 @@
add_setshow_auto_boolean_cmd ("disassemble-next-line", class_stack,
&disassemble_next_line, _("\
-Set whether to disassemble next source line when execution stops."), _("\
-Show whether to disassemble next source line when execution stops."), _("\
-If ON, GDB will display disassembly of the next source line when\n\
-execution of the program being debugged stops.\n\
-If AUTO (which is the default), or there's no line info to determine\n\
-the source line of the next instruction, display disassembly of next\n\
-instruction instead."),
+Set whether to disassemble next source line or insn when execution stops."), _("\
+Show whether to disassemble next source line or insn when execution stops."), _("\
+If ON, GDB will display disassembly of the next source line, in addition\n\
+to displaying the source line itself. If the next source line cannot\n\
+be displayed (e.g., source is unavailable or there's no line info), GDB\n\
+will display disassembly of next instruction instead of showing the\n\
+source line.\n\
+If AUTO (which is the default), display disassembly of next\n\
+instruction only if the source line cannot be displayed.\n\
+If OFF, never display the disassembly of the next source line."),
NULL,
show_disassemble_next_line,
&setlist, &showlist);
next prev parent reply other threads:[~2009-04-17 10:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 17:39 Joel Brobecker
2009-04-16 17:52 ` Eli Zaretskii
2009-04-16 18:02 ` Joel Brobecker
2009-04-16 18:16 ` Eli Zaretskii
2009-04-16 19:07 ` Joel Brobecker
2009-04-16 21:37 ` Eli Zaretskii
2009-04-16 21:54 ` Joel Brobecker
2009-04-16 22:09 ` Pedro Alves
2009-04-17 9:10 ` Eli Zaretskii
2009-04-16 23:57 ` Joel Brobecker
2009-04-17 7:33 ` Hui Zhu
2009-04-17 9:22 ` Eli Zaretskii
2009-04-17 15:50 ` Joel Brobecker
2009-04-17 17:34 ` Daniel Jacobowitz
2009-04-17 22:16 ` Joel Brobecker
2009-04-18 6:48 ` Eli Zaretskii
2009-04-16 22:23 ` Tom Tromey
2009-04-16 23:59 ` Joel Brobecker
2009-04-17 5:33 ` Hui Zhu
2009-04-17 15:57 ` Joel Brobecker
2009-04-17 16:16 ` Tom Tromey
2009-04-17 16:59 ` Hui Zhu
2009-04-17 9:23 ` Eli Zaretskii
2009-04-17 10:05 ` Eli Zaretskii [this message]
2009-04-23 18:49 ` Joel Brobecker
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=83myafk338.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=teawater@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