Re: [rfa/doco] PROBLEMS: add regressions since gdb 6.0

[mec.gnu@mindspring.com (Michael Elizabeth Chastain)]

ac> Er, we already have a repostory of known bugs, it's called the bug 
ac> database.  Why duplicate the content and tracking effort?

Because it works.

The actual part of PROBLEMS that you're objecting to is the paragraphs
which talk about setting breakpoints in constructors in C++ code.
This doesn't work with gcc v3 because gcc v3 emits multiple copies
of the object code, and gdb sets the breakpoint in just one of them.

Before PROBLEMS talked about this, we got several reports per month
about this issue.  Now we don't get any.  And for each user that takes
the trouble to e-mail us, there are many more users who run into the
issue and appreciate having a short description of it.

I think we should keep that part of PROBLEMS as long as gdb has this
problem.

Also, the PR database does not track user-visible bugs.  It has
numerous maintainance entries which do not impact the user at all.

> PROBLEMS should draw the users attention to late breaking and immediate 
> issues that will hurt them (gdb doesn't build, this broke going from the 
> previous release).

Sure.  To me, that means every regression from previous releases,
plus bugs that are likely to be important to a large part of the
user population.

> A bug already present in the previous release _isn't_ new news.

Some of those bugs are important to users, though.

Michael C