From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19965 invoked by alias); 7 Nov 2002 20:21:59 -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 19954 invoked from network); 7 Nov 2002 20:21:57 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 7 Nov 2002 20:21:57 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id gA7JxFw00374 for ; Thu, 7 Nov 2002 14:59:15 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id gA7KLvf13952 for ; Thu, 7 Nov 2002 15:21:57 -0500 Received: from localhost.redhat.com (romulus-int.sfbay.redhat.com [172.16.27.46]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id gA7KLu507026 for ; Thu, 7 Nov 2002 15:21:56 -0500 Received: by localhost.redhat.com (Postfix, from userid 469) id E29E4FF79; Thu, 7 Nov 2002 15:17:48 -0500 (EST) From: Elena Zannoni MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15818.51820.811781.873857@localhost.redhat.com> Date: Thu, 07 Nov 2002 12:21:00 -0000 To: "Garriss, Michael" Cc: "'Mark Crosland'" , gdb@sources.redhat.com Subject: RE: gcc 3.2, gdb 5.2.1, solaris2.8 sparc, slow In-Reply-To: References: X-SW-Source: 2002-11/txt/msg00070.txt.bz2 Garriss, Michael writes: > I second that. > > -----Original Message----- > From: Mark Crosland [mailto:mjc@attbi.com] > Sent: Thursday, November 07, 2002 11:36 AM > To: gdb@sources.redhat.com > Subject: Re: gcc 3.2, gdb 5.2.1, solaris2.8 sparc, slow > > > > OK, I will assume that no response means gdb is not suitable for medium -> > large multi-threaded c++ development on solaris. > > Thanks, > Mark Actually no. gdb should be able to debug such applications. Would you have a chance to poke around gdb and see what it's doing that takes so long? It may be the same thing reported in this thread: http://sources.redhat.com/ml/gdb/2001-10/msg00157.html Maybe the thread maintainers have some additional comments. Elena > > On Wed, 6 Nov 2002, Mark Crosland wrote: > > > > > I noticed a recent thread regarding rather slow response from gdb. I am > > experiencing the same thing on solaris 2.8, sparc platform. It is an > > enterpirse class server, not the fastest thing sun makes, but not slow. > > > > I built gcc 3.2 > > ../configure --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld > > --disable-nls --prefix=/homedir/markc/gcc --enable-languages=c,c++ > > --enable-shared --enable-threads > > > > and then built gdb 5.2.1 > > mkdir build > > cd build > > /full/path/to/configure > > make > > > > using gnu make 3.77 > > > > solaris 2.8 sparc > > > > gdb responds with the most simple programs, but anything that isn't dirt > > simple seems to cause it to take forever to do basic commands. > > > > I do "gdb myProgram", it starts right up, get the gdb prompt. > > > > "info address main" never returns > > "break main" never returns > > > > CPU is peaked by gdb process > > > > If I say "run", it eventualy runs > > > > the program that is being run in gdb runs fine outside the debugger, isn't > > really all that large, runs on several platforms, etc... it does load some > > relatively average sized shared libraries (both from the OS and using > > dlopen()). The program is multi-threaded. > > > > It is a c++ and c program > > > > The modules that contain main are compiled with -g. nm from binutils shows > > lots of symbols. > > > > trying to get away from Sun compiler, but a debugger is a critical > > piece... > > > > ??? > > > > Mark, > >