From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5890 invoked by alias); 20 Jun 2006 22:55:20 -0000 Received: (qmail 5881 invoked by uid 22791); 20 Jun 2006 22:55:20 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Tue, 20 Jun 2006 22:55:18 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1Fsp7r-0001um-O4; Tue, 20 Jun 2006 18:55:15 -0400 Date: Tue, 20 Jun 2006 23:28:00 -0000 From: Daniel Jacobowitz To: Oliver Block Cc: gdb@sourceware.org Subject: Re: how to show cause of segmentation fault with gdb Message-ID: <20060620225515.GA7335@nevyn.them.org> Mail-Followup-To: Oliver Block , gdb@sourceware.org References: <200606210052.45882.lists@block-online.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200606210052.45882.lists@block-online.eu> User-Agent: Mutt/1.5.11+cvs20060403 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-06/txt/msg00159.txt.bz2 On Wed, Jun 21, 2006 at 12:52:45AM +0200, Oliver Block wrote: > Is there a safe way show the cause of that error using gdb. No, not really. -- Daniel Jacobowitz CodeSourcery