Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: David Carlton <carlton@kealia.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Add meaningful section titles to PROBLEMS
Date: Fri, 19 Mar 2004 17:33:00 -0000	[thread overview]
Message-ID: <405B2EF0.6050009@gnu.org> (raw)
In-Reply-To: <yf2y8pwvjyi.fsf@hawaii.kealia.com>


> That aside, I don't like the current design.

[which "current"? :-)]

>  The earlier design had a
> list of (sometimes fairly trivial) regressions since 6.0, coupled with
> a much more serious outstanding problem; these two shouldn't be mixed.
> If we decide that we don't want regressions since 6.0 to be in a
> separate section, then we should apply the same criteria to everything
> listed under the header "C++ support" (or whatever), and decide to
> either only list serious bugs or else list every problem that we know
> about.

The current list of C++ problems needs some serious editing.  For instance:

gdb/1512: no canonical way to output names of C++ types
(which is about gdb printing "const char *" vs "char const *")
can hardly be described as "mission critical".  Contrast it to JeffJ's 
discovery that GDB can't debug an NPTL threaded program that does a 
thread delete/create, outch! (but something we likely won't mention in 
problems).

As for some of the others, I think they would be better served as notes 
in the documentation (i.e., gdb.texinfo).

> 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?

Andrew



  reply	other threads:[~2004-03-19 17:33 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 [this message]
2004-03-19 17:43     ` David Carlton
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=405B2EF0.6050009@gnu.org \
    --to=cagney@gnu.org \
    --cc=carlton@kealia.com \
    --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