From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16537 invoked by alias); 10 Jan 2006 19:16:38 -0000 Received: (qmail 16407 invoked by uid 22791); 10 Jan 2006 19:16:37 -0000 X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO sibelius.xs4all.nl) (82.92.89.47) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 10 Jan 2006 19:16:34 +0000 Received: from elgar.sibelius.xs4all.nl (root@elgar.sibelius.xs4all.nl [192.168.0.2]) by sibelius.xs4all.nl (8.13.4/8.13.4) with ESMTP id k0AJGPv7022514; Tue, 10 Jan 2006 20:16:25 +0100 (CET) Received: from elgar.sibelius.xs4all.nl (kettenis@localhost.sibelius.xs4all.nl [127.0.0.1]) by elgar.sibelius.xs4all.nl (8.13.4/8.13.3) with ESMTP id k0AJGO78018468; Tue, 10 Jan 2006 20:16:24 +0100 (CET) Received: (from kettenis@localhost) by elgar.sibelius.xs4all.nl (8.13.4/8.13.4/Submit) id k0AJGOgg009366; Tue, 10 Jan 2006 20:16:24 +0100 (CET) Date: Tue, 10 Jan 2006 19:16:00 -0000 Message-Id: <200601101916.k0AJGOgg009366@elgar.sibelius.xs4all.nl> From: Mark Kettenis To: rjshaw@netspace.net.au CC: gdb@sources.redhat.com In-reply-to: <43C39AAB.6000505@netspace.net.au> (message from Russell Shaw on Tue, 10 Jan 2006 22:29:47 +1100) Subject: Re: Core dumps References: <43C22DD0.5080503@netspace.net.au> <200601091912.k09JC0fp022663@elgar.sibelius.xs4all.nl> <43C39AAB.6000505@netspace.net.au> 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-01/txt/msg00075.txt.bz2 > Date: Tue, 10 Jan 2006 22:29:47 +1100 > From: Russell Shaw > > I'm using debian-sid. Well, that narrows it down... ...but not nearly enough. Well, I suppose you're on i386 GNU/Linux. > GNU gdb 6.3-debian > gcc (GCC) 4.0.3 20051201 (prerelease) (Debian 4.0.2-5) So that's a Debian-modified gdb, have you tried asking for help on any of the Debian lists? > In gdb, i did: > > (gdb) target core core > (gdb) bt > > I get a long backtrace of "?" and a note saying corrupt stack. > > I can't get a new core file to happen now, despite the > program hitting abort() or raise(11). I have ulimit unlimited. Well, I can't be of much help then. Mark