From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25384 invoked by alias); 29 Aug 2006 13:23:20 -0000 Received: (qmail 25371 invoked by uid 22791); 29 Aug 2006 13:23:20 -0000 X-Spam-Check-By: sourceware.org Received: from smtpsrv20.tdc.dk (HELO smtpsrv20.tdc.dk) (192.66.25.157) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 29 Aug 2006 13:23:15 +0000 Received: from conbr320.tdk.dk ([10.106.95.33]) by smtpsrv20.tdc.dk with Microsoft SMTPSVC(5.0.2195.6982); Tue, 29 Aug 2006 15:25:50 +0200 Received: from conbr101.tdk.dk ([10.106.101.59]) by conbr320.tdk.dk with InterScan Messaging Security Suite; Tue, 29 Aug 2006 15:23:12 +0200 Received: from VESTMB403A.tdk.dk ([10.106.170.54]) by conbr101.tdk.dk with Microsoft SMTPSVC(5.0.2195.6713); Tue, 29 Aug 2006 15:23:12 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: SV: Which thread caused dump? Date: Tue, 29 Aug 2006 13:23:00 -0000 Message-ID: <2B1831460E7C6B46A19066A0E9147A4E0C1743@VESTMB403A.tdk.dk> In-Reply-To: <20060829123901.GA12955@nevyn.them.org> From: "Steffen Schumacher" To: 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-08/txt/msg00214.txt.bz2 Ok but it doesn't show me much. Hmm..=20 My stack must have been overwritten: > (gdb) bt > #0 0x2834f46b in pthread_testcancel () from /usr/lib/libpthread.so.2 > #1 0x28347e3c in pthread_mutexattr_init () from > /usr/lib/libpthread.so.2 > #2 0x284fa450 in ?? () > (gdb) #2 seems to start out of the blue.. How do you go about chasing a bug like this? /Steffen -----Oprindelig meddelelse----- Fra: Daniel Jacobowitz [mailto:drow@false.org]=20 Sendt: 29. august 2006 14:39 Til: Steffen Schumacher Cc: gdb@sourceware.org Emne: Re: Which thread caused dump? On Tue, Aug 29, 2006 at 12:42:40PM +0200, Steffen Schumacher wrote: > Hi! >=20 > I have a multithreaded program which coredumps after ~20 hours of > running. > Is it possible to see which thread caused the crash? > Usually I use thr x and bt for seeing if some exception was thrown, but > I have a case where no thread is throwing any exceptions. >=20 > I've enclosed output from the actual core dump.. any other cmd's I > should know of? > Any help on discovering why it is crashing would be greatly > appreciated.. Generally the first thread that comes up is the one that crashed. > Program terminated with signal 11, Segmentation fault. > * 10 LWP 100080 0x2834f4ab in pthread_testcancel () from > /usr/lib/libpthread.so.2 > (gdb) thr 10 > [Switching to thread 10 (LWP 100080)]#0 0x2834f46b in > pthread_testcancel () from /usr/lib/libpthread.so.2 > (gdb) bt > #0 0x2834f46b in pthread_testcancel () from /usr/lib/libpthread.so.2 > #1 0x28347e3c in pthread_mutexattr_init () from > /usr/lib/libpthread.so.2 > #2 0x284fa450 in ?? () > (gdb) > So probably right there. --=20 Daniel Jacobowitz CodeSourcery