From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14101 invoked by alias); 23 Dec 2002 22:39:57 -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 14094 invoked from network); 23 Dec 2002 22:39:55 -0000 Received: from unknown (HELO zinc.carbondesignsystems.com) (66.166.225.3) by 209.249.29.67 with SMTP; 23 Dec 2002 22:39:55 -0000 Received: (from josh@localhost) by zinc.carbondesignsystems.com (8.11.6/8.11.6) id gBNMdho12723; Mon, 23 Dec 2002 17:39:43 -0500 From: "Joshua D. Marantz" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15879.37039.491529.709506@zinc.carbondesignsystems.com> Date: Mon, 23 Dec 2002 14:39:00 -0000 To: gdb@sources.redhat.com Cc: josh@carbondesignsystems.com Reply-To: josh@carbondesignsystems.com Subject: gdb 5.3 issues with g++ 3.2 on RedHat 7.3 & Solaris 9. X-SW-Source: 2002-12/txt/msg00309.txt.bz2 Hello, We are having trouble debugging C++ code. Are there a number of outstanding issues, or could we have a configuration problem? We have tried a variety of combinations of the following tools: gdb 5.2.1, gdb 5.3 g++ 3.1.1, 3.2, 3.2.1 g++ compile options "-g", "-g3", "-ggdb", "-gstabs", "-gstabs+", "-gdwarf-2" SGI STL & STLport 4.5.3 RedHat 7.3 & Solaris 9 Symptoms include: - breakpoints in constructors do not work. gdb says they get set successfully, but they do not actually break. This occurs whether the constructors are inline or out-of-line. - casting on the command line does not work -- yields a syntax error - printing contents of instances of STL classes sometimes crashes - frequent gdb crashes (sorry this is so vague...) - when compiling with -gstabs+, I can print most structures, but I can't call class methods from gdb. - when compiling with -gdwarf-2, I can call class methods from gdb, but I can't print most structures - calling global functions from the debugger takes a long time and uses a lot of memory. calling class methods is fast however. - it is difficult to call template methods from the debugger All these issues were not present using g++ 2.8.1 and gdb 4.17. In that environment most things worked well Although gdb 4.17 did crash a little too often, it was much more functional. We can't go back to those old tools because our C++ & STL usage goes beyond the capabilities of g++ 2.8.1 & 2.9.*. I can give testcases for all these things but it's really pretty basic C++ debugging. Is this enough information? Is there a path through these tools that works -- e.g. config options, versions, etc? Thanks, -Josh