From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4724 invoked by alias); 18 Apr 2002 10:11:19 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 4683 invoked from network); 18 Apr 2002 10:11:11 -0000 Received: from unknown (HELO is.elta.co.il) (199.203.121.2) by sources.redhat.com with SMTP; 18 Apr 2002 10:11:11 -0000 Received: from is (is [199.203.121.2]) by is.elta.co.il (8.9.3/8.8.8) with SMTP id OAA05946; Thu, 18 Apr 2002 14:08:41 +0300 (IDT) Date: Thu, 18 Apr 2002 03:11:00 -0000 From: Eli Zaretskii X-Sender: eliz@is To: Michael Veksler cc: Andrew Cagney , "H . J . Lu" , gdb@sources.redhat.com Subject: Re: gdb 5.2 removes the conditional breakpoints In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-04/txt/msg00305.txt.bz2 On Thu, 18 Apr 2002, Michael Veksler wrote: > Your argument that "5,2 has been around for ~4 > years" does not hold water, how many people have been using 5.2 ? You misunderstood: Andrew said that between 4.17 and 5.2, all versions of GDB had this bug. Those versions in between are in use for 4 years, not version 5.2 (which wasn't released yet). > The "many > eyeballs" effect takes place only when you "release early, release often" > and 4 years cycle is anything but "often". You misunderstood again: there were several versions of GDB during those 4 years, not one version. > Now that you have a branch, people will start using it. Bugs will be > spotted, some of them will be critical (SEGV), some will be very bad (an > important gdb state gets reset upon restart) and others will be simply > annoying (print syntax will not work the way it is supposed to). Bugs which have relatively safe fixes will be fixed on the branch. Bugs that don't have safe fixes will have to wait for the next release. New features (as opposed to bugfixes) will have to wait, period. Please be aware of the downside of fixing everything indiscriminately: it means that GDB 5.2 will never be released, since ``there's always one more bug''. So what will go into the branch and what won't is a judgement call, not something that is self-evident. > second bug (few hours later), was this conditional breakpoint problem. This > problem is very annoying in C++. Every condition with virtual functions > gets removed (at least those that I tried). Until it gets fixed, you can work around this problem by creating a .gdbinit file which sets all the breakpoints automatically.