From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6153 invoked by alias); 12 Feb 2002 23:02:58 -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 6111 invoked from network); 12 Feb 2002 23:02:57 -0000 Received: from unknown (HELO bunker.fullplaymedia.com) (63.165.188.8) by sources.redhat.com with SMTP; 12 Feb 2002 23:02:57 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: debugging gcc 3.x c++ Date: Tue, 12 Feb 2002 15:02:00 -0000 Message-ID: From: "Dan Conti" To: "Daniel Jacobowitz" Cc: X-SW-Source: 2002-02/txt/msg00193.txt.bz2 > -----Original Message----- > From: Daniel Jacobowitz [mailto:drow@mvista.com] > Subject: Re: debugging gcc 3.x c++ > > [snip] > > This is fixed in GDB CVS. It has been for a bit over a month now.=20 > Could you give it a try? >=20 > I see on the PR trail that I told you this at the time. The > misunderstanding may come from 5.1.1 being released afterwards; that > does NOT contain the fix. 5.2 will. Yes, i remember you telling me that at the time. I tried out a snap from 01/22/02 which seemed to fix it but showed other issues on my target. When 5.1.1 came out, i figured that the existing bugfixes would be incorporated into that release, and when i ran it initially it didn't seem to exhibit this problem (although that could easily be attributed to different test code). Out of curiosity, why wasn't this incorporated into the 5.1.1 release? In any case, when is gdb 5.2 scheduled to be released? If it was just me, i'd use a cvs snapshot, but i have to set this up for a group of people and i'd rather use something more stable. Alternatively, would it be possible for me to patch my 5.1.1 with the appropriate fixes? > Actually, it's for GNATS use only. GNATS messages get copied there. Then perhaps the web page should be updated to mention that it's for GNATS use only? The description indicates that it can be used for discussing bugs submitted to the database, so one would think that discussion this bug (which was submitted to the database) should happen on that list.