Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Hui Zhu <teawater@gmail.com>
Cc: tromey@redhat.com, brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [RFA] Set the default of disassemble-next-line to off
Date: Sat, 25 Apr 2009 09:56:00 -0000	[thread overview]
Message-ID: <83k559f45n.fsf@gnu.org> (raw)
In-Reply-To: <daef60380904222045g258a1913ma0bc47946bba2530@mail.gmail.com>

> Date: Thu, 23 Apr 2009 11:45:59 +0800
> From: Hui Zhu <teawater@gmail.com>
> Cc: tromey@redhat.com, brobecker@adacore.com, gdb-patches@sourceware.org
> 
> Everything of this patch is very clear.
> 
> +If AUTO (which is the default), display disassembly of next\n\
> (which is the default) need move to
> ++If OFF (which is the default) ,
> 
> After updated it, it's OK for me.
> 
> btw, I think gdb.texinfo need this patch too.

I installed the following patch:

2009-04-25  Eli Zaretskii  <eliz@gnu.org>

	* gdb.texinfo (Machine Code) <disassemble-next-line>: Improve and
	clarify the wording.

Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.585
diff -u -r1.585 gdb.texinfo
--- gdb/doc/gdb.texinfo	23 Apr 2009 21:28:20 -0000	1.585
+++ gdb/doc/gdb.texinfo	25 Apr 2009 09:53:08 -0000
@@ -6071,11 +6071,21 @@
 @kindex show disassemble-next-line
 @item set disassemble-next-line
 @itemx show disassemble-next-line
-Control whether or not @value{GDBN} will disassemble next source line
-when execution stops.  If ON, GDB will display disassembly of the next
-source line when execution of the program being debugged stops.
-If AUTO, or there's no line info to determine the source line of the
-next instruction, display disassembly of next instruction instead.
+Control whether or not @value{GDBN} will disassemble the next source
+line or instruction when execution stops.  If ON, @value{GDBN} will
+display disassembly of the next source line when execution of the
+program being debugged stops.  This is @emph{in addition} to
+displaying the source line itself, which @value{GDBN} always does if
+possible.  If the next source line cannot be displayed for some reason
+(e.g., if @value{GDBN} cannot find the source file, or there's no line
+info in the debug info), @value{GDBN} will display disassembly of the
+next @emph{instruction} instead of showing the next source line.  If
+AUTO, @value{GDBN} will display disassembly of next instruction only
+if the source line cannot be displayed.  This setting causes
+@value{GDBN} to display some feedback when you step through a function
+with no line info or whose source file is unavailable.  The default is
+OFF, which means never display the disassembly of the next line or
+instruction.
 @end table
 
 


      reply	other threads:[~2009-04-25  9:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19 13:47 Hui Zhu
2009-04-19 17:43 ` Eli Zaretskii
2009-04-20 16:30   ` Hui Zhu
2009-04-20 18:17 ` Tom Tromey
2009-04-22  6:42   ` Hui Zhu
2009-04-22 17:11     ` Eli Zaretskii
2009-04-22 18:46       ` Tom Tromey
2009-04-25  9:44         ` Eli Zaretskii
2009-04-23  3:46       ` Hui Zhu
2009-04-25  9:56         ` Eli Zaretskii [this message]

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=83k559f45n.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