This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: SV: Which thread caused dump?

From: Daniel Jacobowitz <drow at false dot org>
To: Steffen Schumacher <STEFF at tdc dot dk>
Cc: gdb at sourceware dot org
Date: Tue, 29 Aug 2006 09:27:02 -0400
Subject: Re: SV: Which thread caused dump?
References: <20060829123901.GA12955@nevyn.them.org> <2B1831460E7C6B46A19066A0E9147A4E0C1743@VESTMB403A.tdk.dk>

On Tue, Aug 29, 2006 at 03:23:11PM +0200, Steffen Schumacher wrote:
> Ok but it doesn't show me much. Hmm.. 
> 
> 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?

Maybe try getting system libraries with debugging; GDB has apparently
not got enough information to backtrace out of libpthread.so.2.

-- 
Daniel Jacobowitz
CodeSourcery

References:
- Re: Which thread caused dump?
  - From: Daniel Jacobowitz
- SV: Which thread caused dump?
  - From: Steffen Schumacher

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]