From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: GDB 5.2 or GDB 5.1.1?
Date: Tue, 15 Jan 2002 06:05:00 -0000 [thread overview]
Message-ID: <200201151405.IAA18094@duracef.shout.net> (raw)
Andrew Cagney writes:
> Just a postscript to this. Because the FSF would like to be able to
> spin out a manual based on a current release but are currently fixing
> things I'll very likely end up spinning out a 5.1.1 or 5.1.0.2 (ulgh)
> anyway. The latter is far far easier.
Another constraint: 5.1.0.2 would be unable to debug -gdwarf-2 code
with gcc-HEAD, which is going to become gcc 3.1 eventually.
(I'm bummed because my overnight test run got stuck in the configuration
of gdb 5.1, gcc HEAD, -gdwarf-2, so I had to kludge around that and
start the test script again).
Michael C
next reply other threads:[~2002-01-15 14:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 6:05 Michael Elizabeth Chastain [this message]
2002-01-15 7:43 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2002-01-09 13:57 Andrew Cagney
2002-01-09 15:20 ` Daniel Jacobowitz
2002-01-09 15:30 ` Elena Zannoni
2002-01-09 16:38 ` Andrew Cagney
2002-01-14 20:33 ` Andrew Cagney
2002-01-17 12:52 ` Andrew Cagney
2002-01-17 14:39 ` Andrew Cagney
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=200201151405.IAA18094@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--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