gdb/1716: next command does not work on mips-linux-gnu platform

John Van Horne jvh@tivo.com
Fri Apr 22 22:18:00 GMT 2005


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

From: "John Van Horne" <jvh@tivo.com>
To: <gdb-gnats@sources.redhat.com>
Cc:  
Subject: Re: gdb/1716: next command does not work on mips-linux-gnu platform
Date: Fri, 22 Apr 2005 15:17:41 -0700

 I have encountered this problem with gdb 6.2.1, 6.3 and 6.3.50.20050420.
 I am configuring gdb for mips-linux-gnu, and I'm using gcc-3.3.4 and =
 binutils-2.15.
 
 As a test case I'm running gdb/testsuite/gdb.base/call-strs.exp. For =
 6.3.50.20050420
 the failure I get is:
 
 warning: GDB can't find the start of the function at 0x400cf0.
 
     GDB is unable to find the start of the function at 0x400cf0
 and thus can't determine the size of that function's stack frame.
 This means that GDB may be unable to access that stack frame, or
 the frames below it.
     This problem is most likely caused by an invalid program counter or
 stack pointer.
     However, if you think GDB should simply search farther back
 from 0x400cf0 for code which looks like the beginning of a
 function, you can increase the range of the search using the `set
 heuristic-fence-post' command.
 warning: GDB can't find the start of the function at 0x400cf0.
 ?? ()
 
 
 I get the same results whether I use gdbserver on my mips hardware and =
 run gdb on my
 i686 or run native mips gdb.=20
 
 For what it's worth I can successfully step into a dynamically linked =
 library function
 and then finish it.
 
 I'd be happy to supply you with additional information.
 
 Thanks,
 -John Van Horne



More information about the Gdb-prs mailing list