From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com, gdb@sources.redhat.com
Subject: Re: my 6.0 todo list
Date: Thu, 17 Jul 2003 14:35:00 -0000 [thread overview]
Message-ID: <200307171435.h6HEZ7sb013840@duracef.shout.net> (raw)
On my list:
gdb backtrace bugs
http://sources.redhat.com/gdb/bugs/1250
http://sources.redhat.com/gdb/bugs/1253
http://sources.redhat.com/gdb/bugs/1255
dejagnu build issue
http://sources.redhat.com/gdb/bugs/708
red hat linux 9
elena z how is it going?
Off the top of my head, my test bed isn't producing any regressions
besides the backtrace bugs. But I won't swear that it is clean until
I get out the microscope though.
From my last "5.3 versus HEAD" report,
MI issues
how is MI these days?
x86-64 regressions
how is it these days?
multi-register variables
fixed!
java regression
fixed!
gcc HEAD -gstabs+
The nastiest pr, gcc/10055, got fixed in gcc.
There are other regressions with gcc HEAD with both dwarf-2 and
stabs+ but this does not stop a gdb release.
I will put out a "5.3 versus gdb_6_0-branch" report next week.
I've been hoping for some of the backtrace bugs to get fixed first.
Michael C
next reply other threads:[~2003-07-17 14:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 14:35 Michael Elizabeth Chastain [this message]
2003-07-17 15:37 ` Michal Ludvig
2003-07-17 15:46 ` Elena Zannoni
2003-07-17 16:38 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2003-07-18 18:57 Michael Elizabeth Chastain
[not found] <200307171542.LAA13377@smtp.ott.qnx.com>
2003-07-18 13:00 ` Andrew Cagney
2003-07-18 22:54 ` Andrew Cagney
2003-07-17 16:50 Michael Elizabeth Chastain
2003-07-18 6:41 ` Michal Ludvig
2003-07-17 16:47 Michael Elizabeth Chastain
2003-07-16 23:38 Andrew Cagney
2003-07-17 15:42 ` Alain Magloire
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=200307171435.h6HEZ7sb013840@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