From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18197 invoked by alias); 18 Mar 2004 16:23:55 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 18172 invoked from network); 18 Mar 2004 16:23:54 -0000 Received: from unknown (HELO barry.mail.mindspring.net) (207.69.200.25) by sources.redhat.com with SMTP; 18 Mar 2004 16:23:54 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by barry.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1B40JB-0003b3-00; Thu, 18 Mar 2004 11:23:49 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id A32E34B104; Thu, 18 Mar 2004 11:24:02 -0500 (EST) To: cagney@gnu.org, eliz@elta.co.il Subject: Re: [rfa/doco] PROBLEMS: add regressions since gdb 6.0 Cc: gdb-patches@sources.redhat.com, mec.gnu@mindspring.com Message-ID: <20040318162402.A32E34B104@berman.michael-chastain.com> Date: Thu, 18 Mar 2004 16:23:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-03.o/txt/msg00426.txt Message-ID: <20040318162300.GSR576mH1BX7eU-v3BS4UPwpUNg900DqtbYtSaQedNw@z> 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