This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GDB 6.1 "frozen"


On Fri, 26 Mar 2004 19:29:25 +0200, "Eli Zaretskii" <eliz@gnu.org> said:
>> From: David Carlton <carlton@kealia.com>
>> Date: Fri, 26 Mar 2004 09:00:42 -0800

>> I have mixed feelings about Michael's desire of mentioning
>> everything that could be called a regression, no matter how small,
>> in PROBLEMS.

> Me too.  Do you feel that this specific issue is not important
> enough to be in PROBLEMS?

Personally, I wouldn't list any of the C++ issues other than the
breakpoints in constructors bug.  Michael's reason for want to list
all regressions, if I understand him properly, is so that users can
check to see if anything has changed from 6.0 to 6.1 that would cause
them not to want to upgrade; I have a very hard time imagining a
scenario where any of the C++ issues that are listed would block an
upgrade.

So the only question, in my mind, is what issues are important enough
that users should be warned about them so we don't get lots of bug
reports; the breakpoints in constructors issue seems to me to qualify
(I get asked about that often enough at work) but the other issues
don't.

Having said that, it is the case that I occasionally get asked at work
about why people are getting errors when casting, whereas I never get
asked about problems related to gdb/931, gdb/1512, or gdb/1516.  So I
could see a case for keeping the mention of gdb/1518 in there as well.

David Carlton
carlton@kealia.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]