From: Daniel Jacobowitz <drow@false.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: carlos@baldric.uwo.ca, dave.anglin@nrc-cnrc.gc.ca,
gdb@sources.redhat.com
Subject: Re: gdb 6.0
Date: Mon, 01 Mar 2004 18:14:00 -0000 [thread overview]
Message-ID: <20040301181417.GA4613@nevyn.them.org> (raw)
In-Reply-To: <200403011803.i21I30J6021006@hiauly1.hia.nrc.ca>
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
next prev parent reply other threads:[~2004-03-01 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 18:11 John David Anglin
2004-03-01 18:14 ` Daniel Jacobowitz [this message]
2004-03-01 18:33 ` John David Anglin
2004-03-01 18:36 ` Daniel Jacobowitz
2004-03-01 18:42 ` John David Anglin
2004-03-01 20:14 ` Andrew Cagney
2004-03-01 20:16 ` Daniel Jacobowitz
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=20040301181417.GA4613@nevyn.them.org \
--to=drow@false.org \
--cc=carlos@baldric.uwo.ca \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gdb@sources.redhat.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