From: Daniel Jacobowitz <dan@debian.org>
To: Vince Bridgers <vbridgers@bandspeed.com>
Cc: linux-mips@linux-mips.org
Subject: Re: backtrace issues on GDB 5.3
Date: Fri, 28 Nov 2003 10:34:42 -0500 [thread overview]
Message-ID: <20031128153442.GA6624@nevyn.them.org> (raw)
In-Reply-To: <F2DE90354F0ED94EB7061060D9396547B98C49@mars.bandspeed.com>
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
next prev parent reply other threads:[~2003-11-28 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 13:26 backtrace issues on GDB 5.3 Vince Bridgers
2003-11-27 13:26 ` Vince Bridgers
2003-11-28 15:34 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-01 20:34 Vince Bridgers
2003-12-01 20:34 ` Vince Bridgers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031128153442.GA6624@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=vbridgers@bandspeed.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.