Theres a patch floating around that does just that. Its an obvious
hack. I would like to see something clean get into the mainstream
kernels. Its a real pain not to have cores for threaded code.

It does work, however. It effectively dumps the thread that caused the
fault.

(I have a complimentary hack that will dump the stacks of all the
rest of the threads as well (though its a good trick to get gdb to
interpret this). Available upon request.)

af

On Sun, 25 Feb 2001, Chris Wedgwood wrote:

> On Sat, Feb 24, 2001 at 09:57:44PM +0000, Alan Cox wrote:> > The I/O to dump the core would race other changes on the mm. The> right fix is probably to copy the mm (as fork does) then dump the> copy.> > Stupid question... but since all threads see the same memory space as> each other; can we not lock the entire vma for the process whilst> it's being written out?> > > > --cw> -> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in> the body of a message to majordomo@vger.kernel.org> More majordomo info at http://vger.kernel.org/majordomo-info.html> Please read the FAQ at http://www.tux.org/lkml/>