From: Eli Zaretskii <eliz@gnu.org>
To: teawater <teawater@gmail.com>
Cc: tromey@redhat.com, dje@google.com, pedro@codesourcery.com,
drow@false.org, gdb-patches@sourceware.org
Subject: Re: [RFC] disassemble-next-line
Date: Fri, 13 Mar 2009 09:53:00 -0000 [thread overview]
Message-ID: <ubps5sqmf.fsf@gnu.org> (raw)
In-Reply-To: <daef60380903121655o472538c9h84e25fac3548fb66@mail.gmail.com>
> Date: Fri, 13 Mar 2009 07:55:59 +0800
> From: teawater <teawater@gmail.com>
> Cc: Pedro Alves <pedro@codesourcery.com>, Daniel Jacobowitz <drow@false.org>,
> "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
>
> + add_setshow_enum_cmd ("disassemble-next-line", class_run,
> + disassemble_next_line_enum,
> + &disassemble_next_line, _("\
> +Set debugger's willingness to use disassemble-next-line."), _("\
> +Show debugger's willingness to use disassemble-next-line."), _("\
This self-referential doc string is confusing. I suggest to change to
something like this:
Set whether to disassemble next source line when execution stops.
and similarly for Show.
> +If ON, GDB will disassemble the next source line when execution\n\
> +stops.\n\
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 the next source line cannot be\n\
> +ascertained, the next instruction will be disassembled instead."),
What does it mean ``the next source line cannot be ascertained''?
In any case, instead of ``the next instruction will be disassembled
instead'', I suggest ``display disassembly of the next instruction
instead.''
next prev parent reply other threads:[~2009-03-13 9:46 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
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 [this message]
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=ubps5sqmf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=drow@false.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