From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tromey@redhat.com>,
teawater@gmail.com, pedro@codesourcery.com,
drow@false.org, gdb-patches@sourceware.org
Subject: Re: [RFC] disassemble-next-line
Date: Tue, 10 Mar 2009 02:45:00 -0000 [thread overview]
Message-ID: <e394668d0903091905g6cc29538j231bda3e07f4cc72@mail.gmail.com> (raw)
In-Reply-To: <ufxhmlc18.fsf@gnu.org>
On Mon, Mar 9, 2009 at 12:41 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Cc: Eli Zaretskii <eliz@gnu.org>, Doug Evans <dje@google.com>,
>> Pedro Alves <pedro@codesourcery.com>,
>> Daniel Jacobowitz <drow@false.org>,
>> "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
>> From: Tom Tromey <tromey@redhat.com>
>> Date: Mon, 09 Mar 2009 09:26:03 -0600
>>
>> teawater> +Show debugger's willingness to use disassemble-next-line."), _("\
>> teawater> +If on, gdb will output the assembly codes of next line.\n\
>>
>> This also reads strangely, but I don't have a suggestion for what it
>> ought to say. I think it should at least say when the assembly will
>> be displayed. "assembly codes" in particular sounds odd to me.
>
> How about
>
> If ON, GDB will disassemble next source line.
fwiw, I think it should also indicate _when_ it will disassemble the next line.
E.g.
If ON, GDB will disassemble the next source line when execution stops.
If the next source line cannot be ascertained, the next instruction
will be disassembled instead.
or some such.
[IIRC, that is the intended behaviour.]
$0.02.
next prev parent reply other threads:[~2009-03-10 2:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-08 5:34 teawater
2009-03-09 15:29 ` Tom Tromey
2009-03-09 19:41 ` Eli Zaretskii
2009-03-10 2:45 ` Doug Evans [this message]
2009-03-11 8:32 ` teawater
2009-03-12 23:57 ` teawater
2009-03-13 0:50 ` Pedro Alves
2009-03-13 5:54 ` teawater
2009-03-13 9:53 ` Eli Zaretskii
2009-03-16 7:59 ` teawater
2009-03-16 19:22 ` Eli Zaretskii
2009-03-16 19:40 ` Doug Evans
2009-03-16 19:54 ` Eli Zaretskii
2009-03-17 3:15 ` teawater
2009-03-17 4:52 ` Eli Zaretskii
2009-03-17 5:30 ` teawater
2009-03-17 6:21 ` teawater
2009-03-17 19:03 ` Eli Zaretskii
2009-03-17 23:26 ` teawater
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=e394668d0903091905g6cc29538j231bda3e07f4cc72@mail.gmail.com \
--to=dje@google.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--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