From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] print error message if (auto) disassembly failed
Date: Thu, 16 Apr 2009 22:23:00 -0000 [thread overview]
Message-ID: <m3vdp4b5nr.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090416173918.GP7557@adacore.com> (Joel Brobecker's message of "Thu\, 16 Apr 2009 10\:39\:18 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> (FWIW: I did not realize that GDB would now print the current assembly
Joel> instruction by default when the change came in. I don't think that's
Joel> a useful default based on my own usage, but no big deal)
The default is "auto", which means:
If AUTO (which is the default), or there's no line info to determine
the source line of the next instruction, display disassembly of next
instruction instead. */
But I agree with you that this is the wrong default.
I think the default should be "off".
Tom
next prev parent reply other threads:[~2009-04-16 22:23 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 [this message]
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
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=m3vdp4b5nr.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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