From: Daniel Jacobowitz <drow@mvista.com>
To: Klaus Zeitler <kzeitler@lucent.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb 6.0 backtrace on Solaris 5.8
Date: Wed, 14 Jan 2004 13:53:00 -0000 [thread overview]
Message-ID: <20040114135358.GA2400@nevyn.them.org> (raw)
In-Reply-To: <q5g4quyzph4.fsf@lucent.com>
On Wed, Jan 14, 2004 at 01:25:43PM +0100, Klaus Zeitler wrote:
>
> I'm using gdb 6.0 on solaris 5.8 and I'm having problems with the backtrace
> that gdb 6.0 shows. 'bt' sometimes doesn't show all the calls. I've tried
> a few small example programs, but couldn't reproduce it there :-(.
> Today I tried to look at an emacs (CVS version) crash and here gdb 6.0 refused
> to show any backtrace at all:
You'll want to try a CVS snapshot. Mark has rewritten the SPARC port,
and also fixed a bug that caused backtraces to stop when PC == 0.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-14 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 12:25 Klaus Zeitler
2004-01-14 13:53 ` Daniel Jacobowitz [this message]
2004-01-20 13:47 ` Klaus Zeitler
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=20040114135358.GA2400@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kzeitler@lucent.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox