[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Where's my core file ?
- To: Oded Arbel <odeda-linux-il(at-nospam)betalfa.org.il>
- Subject: Re: Where's my core file ?
- From: Gavrie Philipson <gavrie(at-nospam)philipson.co.il>
- Date: Mon, 20 Aug 2001 20:49:54 +0300
- CC: Linux-IL mailing list <linux-il(at-nospam)cs.huji.ac.il>
- References: <008001c129a0$29306c30$de01000a@oded>
- Sender: gavrie(at-nospam)localhost.localdomain
- Sender: linux-il-bounce(at-nospam)cs.huji.ac.il
Oded Arbel wrote:
>
> Have this really wierd problem with core dumps - we have several computers
> running linux that we use for debugging, with various configurations. on
> most of them (that is all but one) when an application crashes it does not
> always produce a core dump (most times it doesn't) and no - I haven't forgot
> about ulimit. ulimit -c is always set for unlimited.
> Consider, please, the following piece of core :
[deleted]
Hi Oded,
AFAIK, core files are useless when you are using Linux pthreads.
The core file that gets dumped on a crash is the image of the thread
that happened to be running at the moment of the crash, which isn't
necessarily the thread that caused the crash. This seems consistent with
your symptoms.
I seem to recall that there is some very new support for multithreaded
cores, but I don't think it's included in mainstream kernels/libs yet.
Somebody correct me if I'm mistaken.
All this means that multithreaded debugging is indeed harder than it
should be.
-- Gavrie.
=================================================================
To unsubscribe, send mail to linux-il-request@linux.org.il with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail linux-il-request@linux.org.il