From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: eliz@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [rfa/doco] PROBLEMS: add regressions since gdb 6.0
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <4058790B.1080508@gnu.org> (raw)
Message-ID: <20040319000900.iKXYiOhp7o7Is45OBrpRIv2ZQVe1zJGCQF77RNRh7_U@z> (raw)
In-Reply-To: <20040317015343.3DA244B104@berman.michael-chastain.com>
> Here is an update for PROBLEMS.
>
> I added all the regressions that I know about from gdb 6.0 to gdb 6.1.
> I also added some section headers, "Regressions since gdb 6.0"
> and "Regressions since gdb 5.3".
I don't think it should retain regressions since 5.3, the file is
stating problems in this release, not the last one.
Andrew
next prev parent reply other threads:[~2004-03-17 16:13 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 1:53 Michael Elizabeth Chastain
2004-03-17 16:13 ` Andrew Cagney [this message]
2004-03-19 0:09 ` Andrew Cagney
2004-03-17 17:05 ` David Carlton
2004-03-19 0:09 ` David Carlton
2004-03-19 0:09 ` Michael Elizabeth Chastain
2004-03-19 0:09 ` David Carlton
2004-03-17 17:19 ` David Carlton
2004-03-19 0:09 ` Eli Zaretskii
2004-03-17 19:07 ` Eli Zaretskii
2004-03-19 0:09 ` David Carlton
2004-03-17 19:18 ` David Carlton
2004-03-19 0:09 ` Andrew Cagney
2004-03-17 22:11 ` Andrew Cagney
2004-03-19 0:09 ` Eli Zaretskii
2004-03-18 6:11 ` Eli Zaretskii
2004-03-18 16:36 ` Daniel Jacobowitz
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:25 ` Daniel Jacobowitz
2004-03-19 0:09 ` Eli Zaretskii
2004-03-18 16:55 ` Eli Zaretskii
2004-03-19 0:09 ` Eli Zaretskii
2004-03-17 6:16 ` Eli Zaretskii
2004-03-17 18:55 Michael Elizabeth Chastain
2004-03-17 19:03 ` David Carlton
2004-03-19 0:09 ` David Carlton
2004-03-19 0:09 ` Michael Elizabeth Chastain
2004-03-19 0:09 ` David Carlton
2004-03-17 19:16 ` David Carlton
2004-03-17 22:54 Michael Elizabeth Chastain
2004-03-17 23:39 ` Andrew Cagney
2004-03-18 6:16 ` Eli Zaretskii
2004-03-18 16:05 ` Andrew Cagney
2004-03-18 16:52 ` Eli Zaretskii
2004-03-19 0:09 ` Eli Zaretskii
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Eli Zaretskii
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Michael Elizabeth Chastain
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-17 18:21 ` Michael Elizabeth Chastain
2004-03-17 22:11 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-17 19:21 ` Michael Elizabeth Chastain
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-17 20:15 ` Michael Elizabeth Chastain
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-17 19:30 ` Michael Elizabeth Chastain
2004-03-17 19:48 ` David Carlton
2004-03-19 0:09 ` Eli Zaretskii
2004-03-18 6:06 ` Eli Zaretskii
2004-03-19 0:09 ` David Carlton
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-17 6:58 ` Michael Elizabeth Chastain
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-18 16:23 ` Michael Elizabeth Chastain
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:27 ` Daniel Jacobowitz
2004-03-19 14:56 ` Eli Zaretskii
2004-03-19 15:03 ` Andrew Cagney
2004-03-19 15:33 ` Eli Zaretskii
2004-03-19 15:54 ` Andrew Cagney
2004-03-20 15:38 ` Eli Zaretskii
2004-03-19 0:09 ` David Carlton
2004-03-18 16:45 ` David Carlton
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=4058790B.1080508@gnu.org \
--to=cagney@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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