From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: RFC: Backtrace vs. list in recent GDB
Date: Thu, 05 Jun 2003 03:46:00 -0000 [thread overview]
Message-ID: <20030605034652.GA8918@nevyn.them.org> (raw)
Sometime between GDB 5.2 and GDB 5.3, when the default-source-location
code was touched, backtrace began changing the notion of the "current
source location". As a result, if you say "backtrace" and then "list"
now, you get the last listed frame's source location - not the previous
default location. Personally, I think that's wrong. I don't think it
was deliberate, but I might have missed something... any comments?
It seems to me that this doesn't represent any more fundamental bug,
but just that backtrace should save and restore the current source
location. Does anyone else have an opinion, before I implement that?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
reply other threads:[~2003-06-05 3:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030605034652.GA8918@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).