From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>, Baurjan Ismagulov <ibr@ata.cs.hun.edu.tr>
Cc: gdb@sources.redhat.com
Subject: Re: GDB 6.2.1?
Date: Sat, 07 Aug 2004 18:31:00 -0000 [thread overview]
Message-ID: <41152002.9020708@gnu.org> (raw)
In-Reply-To: <41151A34.1000704@gnu.org>
> I'll commit the ``absolute source path'' patch then 6.2.1 is good to go (well depending on how Eli and Mark resolve the i386 change).
I'm going to back out of my decision here :-(
I've looked over the patch and am really reluctant to back-port it
without a testcase illustrating what it fixed. While yes a bug, its not
like the absolute shocker MIPS crash in 6.2. It's also long standing.
I think for this we should instead accelerate 6.3 a little and pull it
into the Oct/Nov timeframe.
Andrew
next prev parent reply other threads:[~2004-08-07 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 19:52 Andrew Cagney
2004-08-05 20:13 ` Michael Chastain
2004-08-05 20:48 ` Joel Brobecker
2004-08-06 15:10 ` Andrew Cagney
2004-08-06 16:16 ` Joel Brobecker
2004-08-07 18:06 ` Andrew Cagney
2004-08-07 18:31 ` Andrew Cagney [this message]
2004-08-08 4:00 ` Eli Zaretskii
2004-08-08 12:00 ` Baurjan Ismagulov
2004-08-13 13:50 ` 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=41152002.9020708@gnu.org \
--to=cagney@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=ibr@ata.cs.hun.edu.tr \
/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