* RFC: Backtrace vs. list in recent GDB
@ 2003-06-05 3:46 Daniel Jacobowitz
0 siblings, 0 replies; only message in thread
From: Daniel Jacobowitz @ 2003-06-05 3:46 UTC (permalink / raw)
To: gdb
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-06-05 3:46 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-06-05 3:46 RFC: Backtrace vs. list in recent GDB Daniel Jacobowitz
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).