From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, gdb@sources.redhat.com
Subject: Re: GDB 6.1 branch 2004-02-26-gmt
Date: Fri, 20 Feb 2004 01:19:00 -0000 [thread overview]
Message-ID: <20040220011823.848FD4B104@berman.michael-chastain.com> (raw)
Well, the regression list I have is:
http://sources.redhat.com/gdb/bugs/826
variables in C++ namespacs have to be enclosed in quotes
http://sources.redhat.com/gdb/bugs/931
GDB could be more generous when reading types C++ templates on input
http://sources.redhat.com/gdb/bugs/1505
[regression] gdb prints a bad backtrace for a thread
http://sources.redhat.com/gdb/bugs/1512
no canonical way to output names of C++ types
http://sources.redhat.com/gdb/bugs/1516
[regression] local classes, gcc 2.95.3, dwarf-2
These are regressions from gdb 6.0 to gdb HEAD.
I'm comfortable documenting them in PROBLEMS and leaving these
bugs in 6.1.
Michael C
next reply other threads:[~2004-02-20 1:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 1:19 Michael Elizabeth Chastain [this message]
2004-02-21 16:14 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2004-02-20 0:34 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=20040220011823.848FD4B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--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