From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16180 invoked by alias); 14 May 2008 22:15:12 -0000 Received: (qmail 16170 invoked by uid 22791); 14 May 2008 22:15:11 -0000 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 14 May 2008 22:14:40 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id DCEBD2A9984; Wed, 14 May 2008 18:14:38 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 8vHiV8540hUa; Wed, 14 May 2008 18:14:38 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id A18E32A997F; Wed, 14 May 2008 18:14:38 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 85DDCE7ACD; Wed, 14 May 2008 15:14:36 -0700 (PDT) Date: Wed, 14 May 2008 22:15:00 -0000 From: Joel Brobecker To: Carlos Eduardo Seo Cc: GDB Mailing List Subject: Re: GDB can't run any binaries Message-ID: <20080514221436.GB3657@adacore.com> References: <482B53C1.3030806@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <482B53C1.3030806@linux.vnet.ibm.com> User-Agent: Mutt/1.4.2.2i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-05/txt/msg00118.txt.bz2 > (gdb) r > Starting program: /home/cseo/test/build/gdb/gdb > > Program received signal SIGSEGV, Segmentation fault. > 0x67ec1f82 in ?? () Hmm, I'm getting pretty standard results with a clean build: # of expected passes 12553 # of unexpected failures 25 # of unexpected successes 1 # of expected failures 40 # of known failures 57 # of unresolved testcases 1 # of untested testcases 8 # of unsupported tests 16 gdb version 6.8.50.20080514-cvs I also was able to start GDB and debug GDB with it, so it's probably a problem on your side. -- Joel