This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: backtrace/1969: backtrace changes currently selected source line


The following reply was made to PR backtrace/1969; it has been noted by GNATS.

From: Jonathan Larmour <jifl@jifvik.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-gnats@sources.redhat.com
Subject: Re: backtrace/1969: backtrace changes currently selected source line
Date: Wed, 13 Jul 2005 16:46:57 +0100

 Daniel Jacobowitz wrote:
 > On Tue, Jul 12, 2005 at 03:51:23PM -0000, jiflgdb@jifvik.org wrote:
 > 
 >>The 'backtrace' command affects the source line chosen for 'list' and
 >>others. This means that doing a list after a backtrace returns the
 >>source line context of the outermost frame. I understood 'backtrace'
 >>was not meant to change the currently selected source line.
 >>
 >>The issue seems to be that stack.c:backtrace_command() calls
 >>stack.c:print_frame_info() which calls
 >>set_current_source_symtab_and_line().
 > 
 > 
 > Have you tried this in CVS HEAD?  I think it was fixed.
 
 I hadn't tried it, but looking at the code, you appear to be right. I'll 
 take it on trust and close the bug.
 
 Thanks
 
 Jifl
 -- 
 --["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]