From: Kevin Buettner <kev@primenet.com>
To: LinuxPPC Developers List <linuxppc-dev@lists.linuxppc.org>
Cc: darkmane@w-link.net
Subject: Re: Help w/ gdb
Date: Sat, 26 Feb 2000 09:35:24 -0700 [thread overview]
Message-ID: <1000226163524.ZM9177@saguaro.lan> (raw)
In-Reply-To: Sean Chitwood <darkmane@w-link.net> "Help w/ gdb" (Jan 15, 11:12pm)
On Jan 15, 11:12pm, Sean Chitwood wrote:
[Regarding gdb...]
> When I attempt to debug an assert/crash as I bring up the stack
> trace I notice that some of the frames point only to the ending
> curly brace of a function (Not always the one it says is being
> debugged). I cannot examine variables, or learn anything else
> productive about the situation.
I had sent some earlier replies to Sean suggesting a couple of
workarounds. These workarounds should no longer be necessary if you
build gdb with the current development sources from
sourceware.cygnus.com.
See http://sourceware.cygnus.com/gdb for more information on how to
download these sources. (If you're going to download via ftp, you'll
want to wait for next week's snapshot as it will contain several
shared library fixes.)
Kevin
--
Kevin Buettner
kev@primenet.com, kevinb@redhat.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-26 16:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-15 21:36 Mac-On-Linux Mailing Lists Dan Burcaw
2000-01-16 7:12 ` Help w/ gdb Sean Chitwood
2000-01-16 16:46 ` Kevin Buettner
2000-01-17 22:02 ` Sean Chitwood
2000-02-26 16:35 ` Kevin Buettner [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-01-16 20:41 D.J. Barrow
[not found] <1000117223224.ZM16757@saguaro.lan>
2000-01-18 0:40 ` Sean Chitwood
2000-01-18 2:04 ` Kevin Buettner
2000-02-16 19:11 Pierre Sarrazin
2000-02-16 19:31 ` Kevin Buettner
2000-02-26 16:23 ` Kevin Buettner
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=1000226163524.ZM9177@saguaro.lan \
--to=kev@primenet.com \
--cc=darkmane@w-link.net \
--cc=linuxppc-dev@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).