From: Hui Zhu <teawater@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com, brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [RFA] Set the default of disassemble-next-line to off
Date: Thu, 23 Apr 2009 03:46:00 -0000 [thread overview]
Message-ID: <daef60380904222045g258a1913ma0bc47946bba2530@mail.gmail.com> (raw)
In-Reply-To: <83eivkhavi.fsf@gnu.org>
On Thu, Apr 23, 2009 at 01:11, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Wed, 22 Apr 2009 14:42:36 +0800
>> From: Hui Zhu <teawater@gmail.com>
>> Cc: Joel Brobecker <brobecker@adacore.com>, Eli Zaretskii <eliz@gnu.org>,
>> "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
>>
>> On Tue, Apr 21, 2009 at 02:16, Tom Tromey <tromey@redhat.com> wrote:
>> >>>>>> "Hui" == Hui Zhu <teawater@gmail.com> writes:
>> >
>> > Hui> -If AUTO (which is the default), or there's no line info to determine\n\
>> > Hui> +If AUTO, or there's no line info to determine\n\
>> > Hui> the source line of the next instruction, display disassembly of next\n\
>> > Hui> instruction instead."),
>> >
>> > It seems to me that this should read:
>> >
>> > If AUTO, and there's no line info to determine [...]
>>
>> If auto:
>> if this is no line info, it will output the next instruction.
>> if this is line inof, it will output nothing.
>>
>> If on:
>> if this is no line info, it will output the next instruction.
>> if this is line inof, it will display disassembly of the next source
>> line whenexecution of the program being debugged stops.
>>
>> If off,
>> it will output nothing.
>>
>>
>> I have no idea to write it clear.
>> Could you please help me with it?
>
> I already suggested a change in the doc string, see
>
> http://sourceware.org/ml/gdb-patches/2009-04/msg00416.html
>
> I didn't see any responses. If the text I suggest there is clear, I
> will fix the manual as well.
>
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.
Thanks,
Hui
next prev parent reply other threads:[~2009-04-23 3:46 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 [this message]
2009-04-25 9:56 ` Eli Zaretskii
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=daef60380904222045g258a1913ma0bc47946bba2530@mail.gmail.com \
--to=teawater@gmail.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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