From: Andrew Cagney <cagney@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB 6.2.1?
Date: Sat, 07 Aug 2004 18:06:00 -0000 [thread overview]
Message-ID: <41151A34.1000704@gnu.org> (raw)
In-Reply-To: <20040806161616.GO1192@gnat.com>
>>>>> >>What's left for this re-spin?
>>>>
>>>>>> >>>- ``absolute source path'' patch
>>>>>> >>>- i386 patch
>>>>>> >>>- ?
>>
>>>
>>> The MIPS crasher bug is in though. That's the critical one.
>
>
> Actually, no, the crasher bug is still not fixed (it's the one
> dealing with the size of long doubles). The patch that we checked in
> was fixing "break main".
``break main'' was, for me the crasher bug :-) The criteria explicitly
mention ``does it fix "break main; run"'' which it did :-)
As for the FP crash, thanks to your bug analysis there's something to
stop it in the branch and a mainline fix is well in hand.
>>> I don't even remember what that one is. Ah, yes, the backtrace fix,
>>> leave that for 6.3.
>
>
> It fixes the backtrace problem, but the problem it fixes also influences
> next/step.
I still think we're better off shooting for a decent clean-up by 6.3 (in
a few months).
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).
Andrew
next prev parent reply other threads:[~2004-08-07 18:06 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 [this message]
2004-08-07 18:31 ` Andrew Cagney
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=41151A34.1000704@gnu.org \
--to=cagney@gnu.org \
--cc=brobecker@gnat.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