From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@cygnus.com, aj@suse.de
Cc: gdb@sources.redhat.com
Subject: Re: 5.1.1
Date: Wed, 19 Dec 2001 13:12:00 -0000 [thread overview]
Message-ID: <200112192111.PAA25951@duracef.shout.net> (raw)
Andreas Jaegar writes:
> That would be fine. GCC has now switched using Dwarf2 as normal
> debugging format and gdb 5.1 cannot read it. I haven't tried the CVS
> version yet whether this is fixed. But having a gdb that can debug
> programs that GCC generates would justify a 5.1.1.
Happily, this has been fixed on the CVS 5.1 branch as well as the CVS
mainline. My experience is that the released version of gdb 5.1 can
handle dwarf2 executables produced by gcc 3.0.2, but not gcc CVS HEAD.
So we are not in a horrible "latest released tools don't work together"
state until gcc releases again.
Some unadorned tables for the CVS 5.1 branch are here:
http://www.shout.net/~mec/sunday/2001-12-06/index.html
Michael C
next reply other threads:[~2001-12-19 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 13:12 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-19 1:54 5.1.1 Andrew Cagney
2001-12-19 2:22 ` 5.1.1 Andreas Jaeger
2001-12-19 2:27 ` 5.1.1 Joel Brobecker
2001-12-19 2:29 ` 5.1.1 Andreas Jaeger
2001-12-19 2:38 ` 5.1.1 Andrew Cagney
2001-12-19 9:27 ` 5.1.1 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=200112192111.PAA25951@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@cygnus.com \
--cc=aj@suse.de \
--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