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]

backtrace/1759: selecting a frame by its address does not work


>Number:         1759
>Category:       backtrace
>Synopsis:       selecting a frame by its address does not work
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Aug 25 09:58:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     ivantchek@yahoo.com
>Release:        6.1
>Organization:
>Environment:
Linux 2.4.25 #4 Mon May 10 18:04:43 CEST 2004 i686 GNU/Linux
version gcc 3.3.4 (Debian 1:3.3.4-4)
This GDB was configured as "i386-linux".
>Description:
GDB documentation states that it is possible to select a frame using either 'frame #N' or 'frame ADDR'. The latter does not seem to work at all, it always yields the following result:

#0  0x00000000 in ?? ()
>How-To-Repeat:
Launch a gdb session, stop at any point. Then get the current frame address ADDR with 'info frame'. Try to use this address with 'frame ADDR'...
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


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