From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24148 invoked by alias); 5 Apr 2005 05:40:54 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 23999 invoked from network); 5 Apr 2005 05:40:42 -0000 Received: from unknown (HELO cat.co.za) (196.33.33.51) by sourceware.org with SMTP; 5 Apr 2005 05:40:42 -0000 Received: (qmail 32354 invoked by uid 1002); 5 Apr 2005 05:57:43 -0000 Received: from stuartb@cat.co.za by mail.cat.co.za by uid 807 with qmail-scanner-1.21 (clamscan: 0.70. Clear:RC:1(196.33.33.52):. Processed in 1.651141 secs); 05 Apr 2005 05:57:43 -0000 Received: from unknown (HELO STU95) (196.33.33.52) by 0 with SMTP; 5 Apr 2005 05:57:41 -0000 Message-ID: <0fb501c539a1$e53857c0$5e22a8c0@STU95> From: "Stuart Brooks" To: "Nathan J. Williams" Cc: References: <0f4601c538fc$30c35970$5e22a8c0@STU95> Subject: Re: gdb 5.3nb1 crashing when accessing elements in static libs Date: Tue, 05 Apr 2005 05:40:00 -0000 Organization: Intervid Technologies MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-SW-Source: 2005-04/txt/msg00036.txt.bz2 > > 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 > > , 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?)?