thread register state information invalid in core files
Daniel Jacobowitz
drow@false.org
Tue Mar 28 22:01:00 GMT 2006
On Tue, Mar 28, 2006 at 05:20:22PM +0200, Balazs Scheidler wrote:
> So it seems to be a kernel bug. Any hints where this was fixed or whether
> it was fixed at all?
Sorry, I've no idea. If it still occurs in current kernel.org kernels,
you may want to report it to the kernel bugzilla.
> > > The funny part that the segfault
> > > itself occurred in the PID number 31158 (not the main thread for sure),
> > > but gdb lists pid 31158 as the main thread with the main thread's stack.
> >
> > The kernel always dumps the faulting thread first.
>
> Sure, but it has the context of the main thread.
Oh, I think I misunderstood you. You've got the main thread's
registers, but the faulting thread's PID? I have no idea how that
could happen!
--
Daniel Jacobowitz
CodeSourcery
More information about the Gdb
mailing list