From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: teawater <teawater@gmail.com>,
tromey@redhat.com, pedro@codesourcery.com,
drow@false.org, gdb-patches@sourceware.org
Subject: Re: [RFC] disassemble-next-line
Date: Mon, 16 Mar 2009 19:40:00 -0000 [thread overview]
Message-ID: <e394668d0903161231w7c2c7268w6f0ba1e3d8ebf7d4@mail.gmail.com> (raw)
In-Reply-To: <umyblqnp2.fsf@gnu.org>
On Mon, Mar 16, 2009 at 12:20 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Mon, 16 Mar 2009 14:51:51 +0800
>> From: teawater <teawater@gmail.com>
>> Cc: tromey@redhat.com, dje@google.com, pedro@codesourcery.com, drow@false.org,
>> gdb-patches@sourceware.org
>>
>> I had make the patches for code and doc.
>> Please help me review it.
>
> Thanks. Everything is OK, except that you didn't answer my question:
>
>> >> +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''?
>
> I asked that question because I cannot understand the last sentence,
> which uses this phrase. Please help me understand what you mean.
>
The issue here is that not all pc values have an associated source
line, and therefore what does one print in this situation?
Whatever you suggest for how to communicate this to the user is fine
with me (fwiw of course).
next prev parent reply other threads:[~2009-03-16 19:32 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
2009-03-16 7:59 ` teawater
2009-03-16 19:22 ` Eli Zaretskii
2009-03-16 19:40 ` Doug Evans [this message]
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=e394668d0903161231w7c2c7268w6f0ba1e3d8ebf7d4@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