From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15513 invoked by alias); 6 Dec 2002 04:45:10 -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 15505 invoked from network); 6 Dec 2002 04:45:09 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by sources.redhat.com with SMTP; 6 Dec 2002 04:45:09 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id gB64j7d21501; Thu, 5 Dec 2002 22:45:07 -0600 Date: Thu, 05 Dec 2002 20:45:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200212060445.gB64j7d21501@duracef.shout.net> To: drow@mvista.com, mn216@columbia.edu Subject: Re: help: gdb and c++ strings Cc: gdb@sources.redhat.com X-SW-Source: 2002-12/txt/msg00114.txt.bz2 Hello Murad, There are two snapshots available: ftp://sources.redhat.com/pub/gdb/snapshots/branch/gdb-5.2.91.tar.bz2 ftp://sources.redhat.com/pub/gdb/snapshots/current/insight+dejagnu-weekly-CVS-20021206.tar.bz2 The first snapshot is from the 5.3 branch and will become gdb 5.3 soon if everything goes well. I am regression testing this right now versus 5.2.1 and there are no big obvious problems yet. The second snapshot is from the CVS head. It's more likely to have the bug fix that Daniel J is referring to. It's also possible that it has build problems because the configuration+build machinery is in active development right now. If it builds, though, it is also in good shape for gcc v3 dwarf-2 debugging. You are on the right track with gcc 3.2.1 and -gdwarf-2. I recommend you try the "branch" snapshot first; it is much more stable. If it is not featureful enough (does not fix your problems) then try the "current" snapshot. Hope this helps, Michael C P. S. I see you are at columbia.edu. I am on Staten Island. Isn't the city beautiful with today's snow?