From: David Carlton <carlton@kealia.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Add meaningful section titles to PROBLEMS
Date: Fri, 19 Mar 2004 17:43:00 -0000 [thread overview]
Message-ID: <yf2ptb8vijv.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <405B2EF0.6050009@gnu.org> (Andrew Cagney's message of "Fri, 19 Mar 2004 12:33:36 -0500")
On Fri, 19 Mar 2004 12:33:36 -0500, Andrew Cagney <cagney@gnu.org> said:
>> That aside, I don't like the current design.
> [which "current"? :-)]
Sorry, I meant "your proposed".
> As for some of the others, I think they would be better served as
> notes in the documentation (i.e., gdb.texinfo).
That's a good point - if we want to make users aware of certain
well-known bugs, then gdb.texinfo is a much more visible place than
PROBLEMS. (Nobody will see PROBLEMS other than possibly the specific
individual, if any, who is installing that version of GDB by hand.)
GCC has a section of known bugs in its manual; we should follow suit.
>> Personally, the old division makes more sense to me: a list of all
>> regressions, plus some more serious outstanding issues. Obviously the
>> header "Regressions since 5.3" should be changed, however.
> How about: serious problems that have been fixed in the mainline but
> are too nasty to backport?
The "breakpoints in constructors" bug isn't fixed in mainline,
either.
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2004-03-19 17:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 16:16 Andrew Cagney
2004-03-19 17:13 ` David Carlton
2004-03-19 17:33 ` Andrew Cagney
2004-03-19 17:43 ` David Carlton [this message]
2004-03-19 19:59 ` Andrew Cagney
2004-03-20 15:22 ` Eli Zaretskii
2004-03-20 15:29 ` Eli Zaretskii
2004-03-20 15:34 ` Eli Zaretskii
2004-03-25 21:07 ` Andrew Cagney
2004-03-19 16:50 Michael Elizabeth Chastain
2004-03-19 17:22 ` Andrew Cagney
2004-03-19 17:45 Michael Elizabeth Chastain
2004-03-20 15:26 ` Eli Zaretskii
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=yf2ptb8vijv.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@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