From: "Stuart Brooks" <stuartb@cat.co.za>
To: "Nathan J. Williams" <nathanw@wasabisystems.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: gdb 5.3nb1 crashing when accessing elements in static libs
Date: Tue, 05 Apr 2005 05:40:00 -0000 [thread overview]
Message-ID: <0fb501c539a1$e53857c0$5e22a8c0@STU95> (raw)
In-Reply-To: <mtu1x9qtqoi.fsf@contents-vnder-pressvre.mit.edu>
> > I am experiencing problems when interrogating a core file - as soon
as I
> > try to access a global variable in a statically linked library or
view
> > the internals of a class/struct declared in a static lib gdb either
says
> > <unknown type>, gives garbage or segmentation faults. Details of my
> > system are:
> >
> > OS: Netbsd 2.0
> > gdb: 5.3nb1
> > compiler: g++ 3.3
>
> I'm assuming this is i386? You're going to be in some pain with C++ on
> this combination; netbsd/i386 2.0 sets gcc to use the stabs debugging
> format by default instead of dwarf-2, because of a bug in 3.3's dwarf
> generation (netbsd PR #25094; equivalent to GCC bug #16788) [I'm not
> at all sure that this is the right tradeoff for that bug].
Yes, this is i386 :( What would you recommend I do? I suppose I could
install a later version of gcc (seems 3.4.0 has this fixed) but I would
imagine that that will need a full system rebuild depending on the
compatibility between 3.3.3 and 3.4.0. Or is there some easier solution,
maybe setting g++ to use dwarf-2 and accepting that the offset for long
long structs will be incorrect (is this a train smash?)?
next prev parent reply other threads:[~2005-04-05 5:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 9:54 Stuart Brooks
2005-04-04 13:39 ` Daniel Jacobowitz
2005-04-04 17:09 ` Nathan J. Williams
2005-04-05 5:40 ` Stuart Brooks [this message]
2005-04-05 7:51 ` Stuart Brooks
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='0fb501c539a1$e53857c0$5e22a8c0@STU95' \
--to=stuartb@cat.co.za \
--cc=gdb@sources.redhat.com \
--cc=nathanw@wasabisystems.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