From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4287 invoked by alias); 1 Mar 2004 18:14:26 -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 4280 invoked from network); 1 Mar 2004 18:14:25 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 1 Mar 2004 18:14:25 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1Axrvl-0001Cj-PT; Mon, 01 Mar 2004 13:14:17 -0500 Date: Mon, 01 Mar 2004 18:14:00 -0000 From: Daniel Jacobowitz To: John David Anglin Cc: carlos@baldric.uwo.ca, dave.anglin@nrc-cnrc.gc.ca, gdb@sources.redhat.com Subject: Re: gdb 6.0 Message-ID: <20040301181417.GA4613@nevyn.them.org> Mail-Followup-To: John David Anglin , carlos@baldric.uwo.ca, dave.anglin@nrc-cnrc.gc.ca, gdb@sources.redhat.com References: <200403011803.i21I30J6021006@hiauly1.hia.nrc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200403011803.i21I30J6021006@hiauly1.hia.nrc.ca> User-Agent: Mutt/1.5.1i X-SW-Source: 2004-03/txt/msg00003.txt.bz2 On Mon, Mar 01, 2004 at 01:03:00PM -0500, John David Anglin wrote: > High c., > > Have you started work on gdb? This weekend I was working on a patch > for the GCC testsuite to make it correctly honor a preexisting > LD_LIBRARY_PATH. This exposed a couple of problems related to > dwarf2 exception support (e.g., g++.dg/eh/forced1.C). This test > passes with sjlj exceptions but fails with dwarf2 exceptions. I > started trying to debug this but found gdb dumps core trying to > read the symbol table of libgcc_s.so.2 :( > > (gdb) sharedlibr /home/dave/gcc-3.5/objdir/gcc/libgcc_s.so.2 > Reading symbols from /home/dave/gcc-3.5/objdir/gcc/libgcc_s.so.2...done. > Loaded symbols for /home/dave/gcc-3.5/objdir/gcc/libgcc_s.so.2 > Segmentation fault (core dumped) GDB 6.0 can't be used with GCC 3.4/3.5, for this exact reason. I think it's caused by var-tracking; you might be able to turn that off separately. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer