linux-mips
[Top] [All Lists]

RE: backtrace issues on GDB 5.3

To: "Daniel Jacobowitz" <dan@debian.org>
Subject: RE: backtrace issues on GDB 5.3
From: "Vince Bridgers" <vbridgers@bandspeed.com>
Date: Mon, 1 Dec 2003 14:34:13 -0600
Cc: <linux-mips@linux-mips.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
Sender: linux-mips-bounce@linux-mips.org
Thread-index: AcO1xSYxzC0J+fJuT9ek328zeMIppAChSr3w
Thread-topic: backtrace issues on GDB 5.3
Tried it. It does work "better", but not "much better".

Thanks for the tip


-----Original Message-----
From: Daniel Jacobowitz [mailto:dan@debian.org] 
Sent: Friday, November 28, 2003 9:35 AM
To: Vince Bridgers
Cc: linux-mips@linux-mips.org
Subject: Re: backtrace issues on GDB 5.3

On Thu, Nov 27, 2003 at 07:26:59AM -0600, Vince Bridgers wrote:
> I'm using GDB 5.3 for mipsel cross-compiled on an x86 box running
RedHat
> 7.3. When I try to use the backtrace capability from GDB most of the
> time I do not get a full stack context - I usually just get the
function
> I'm in at the time. I'm using GCC 3.2 to compile the kernel,
> cross-compiled the same way. I've tried making sure the
> omit-frame-pointer option and the "no instruction schedule" options
are
> on for when we do source level debugging with no joy.  
> 
> Does backtrace work for GCC and GDB cross compiled for mipsel? If so,
> can someone briefly outline the "known good" configuration (GCC/GDB
> versions, + relevant configuration options)?

Not excellently, but definitely better - try the most recent GDB
release.

I have a number of ugly local patches that I hope to clean up for 6.1,
if I have time.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

<Prev in Thread] Current Thread [Next in Thread>
  • RE: backtrace issues on GDB 5.3, Vince Bridgers <=