From: Hui Zhu <teawater@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tromey@redhat.com>,
gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFA] print error message if (auto) disassembly failed
Date: Fri, 17 Apr 2009 16:59:00 -0000 [thread overview]
Message-ID: <daef60380904170959g4c667ab0t71b19f5918b2f2ea@mail.gmail.com> (raw)
In-Reply-To: <20090417155740.GU7585@adacore.com>
Agree with you.
I will post a patch for it.
Thanks,
Hui
On Fri, Apr 17, 2009 at 23:57, Joel Brobecker <brobecker@adacore.com> wrote:
>> In before, when the user step into the program that don't have line
>> message, they will lost the the help from debuger. They will not
>> know what will happen in next except a pc address.
>
> IMO, the vast majority of gdb users will not care, or even understand
> what the instruction means. Most of the time, the only reason I would
> personally land in code that doesn't have any debugging info is when
> attaching to a program, loading a core file, or pressing control-c.
> In such cases, the first thing I usually do is "break ...; continue".
>
> I have very very very occasionally done stepi's that got me inside
> such code, but in that case, I use a special user-defined command
> that does the stepi and then prints the instruction.
>
>> For now, this auto will auto output the asm code. I think it will
>> make user experience (special for new user) better.
>> And I think Joel's patch fix the bug.
>
> It's not just about the bug, actually - I wasn't suggesting that
> we change the default as a way to make it go away. Rather, I think
> that this default setting will be useful to only very few people,
> while at the same time creating the equivalent of noise for the
> rest of the population. This is why I maintain my suggestion of
> changing the default to "off".
>
> --
> Joel
>
next prev parent reply other threads:[~2009-04-17 16:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 17:39 Joel Brobecker
2009-04-16 17:52 ` Eli Zaretskii
2009-04-16 18:02 ` Joel Brobecker
2009-04-16 18:16 ` Eli Zaretskii
2009-04-16 19:07 ` Joel Brobecker
2009-04-16 21:37 ` Eli Zaretskii
2009-04-16 21:54 ` Joel Brobecker
2009-04-16 22:09 ` Pedro Alves
2009-04-17 9:10 ` Eli Zaretskii
2009-04-16 23:57 ` Joel Brobecker
2009-04-17 7:33 ` Hui Zhu
2009-04-17 9:22 ` Eli Zaretskii
2009-04-17 15:50 ` Joel Brobecker
2009-04-17 17:34 ` Daniel Jacobowitz
2009-04-17 22:16 ` Joel Brobecker
2009-04-18 6:48 ` Eli Zaretskii
2009-04-16 22:23 ` Tom Tromey
2009-04-16 23:59 ` Joel Brobecker
2009-04-17 5:33 ` Hui Zhu
2009-04-17 15:57 ` Joel Brobecker
2009-04-17 16:16 ` Tom Tromey
2009-04-17 16:59 ` Hui Zhu [this message]
2009-04-17 9:23 ` Eli Zaretskii
2009-04-17 10:05 ` Eli Zaretskii
2009-04-23 18:49 ` Joel Brobecker
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=daef60380904170959g4c667ab0t71b19f5918b2f2ea@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