Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Stuart Brooks <stuartb@cat.co.za>
Cc: gdb@sources.redhat.com
Subject: Re: gdb 5.3nb1 crashing when accessing elements in static libs
Date: Mon, 04 Apr 2005 13:39:00 -0000	[thread overview]
Message-ID: <20050404133903.GB32163@nevyn.them.org> (raw)
In-Reply-To: <0f4601c538fc$30c35970$5e22a8c0@STU95>

On Mon, Apr 04, 2005 at 11:53:39AM +0200, Stuart Brooks wrote:
> Hi,
> 
> I'm new to this list, so if this is not the right place to be posting
> please let me know....
> 
> 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
> 
> Using the same code, gdb works fine on [Netbsd 1.5.1,gdb 4.17,g++
> 2.91.66] and [Netbsd 1.6.2,gdb 5.0nb1,g++ 2.95.3] so it looks to me like
> a conflict between g++ and gdb. The libs are being compiled with -g and
> without optimizations. I'm really not too sure what to do from here. Any
> ideas/help would be much appreciated ...

You should try a more recent version of GDB.  The latest release is
6.3, and the CVS has an additional almost-year of development.

> Also when trying to print out the value of a global pointer I get this:
> 
> (gdb) p server
> $5 = 134692864

Probably server has no debug information in your object.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-04-04 13:39 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 [this message]
2005-04-04 17:09 ` Nathan J. Williams
2005-04-05  5:40   ` Stuart Brooks
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=20050404133903.GB32163@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=stuartb@cat.co.za \
    /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