From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id PAA31049; Thu, 16 Aug 2001 15:30:42 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id PAA30913 for ; Thu, 16 Aug 2001 15:30:41 +0200 (MET DST) Received: from ontil.ihep.su (ontil.ihep.su [194.190.161.63]) by nez-perce.inria.fr (8.11.1/8.10.0) with ESMTP id f7GD95525751; Thu, 16 Aug 2001 15:09:06 +0200 (MET DST) Received: from localhost (vsl@localhost) by ontil.ihep.su (8.11.0/8.11.0) with ESMTP id f7GCj4g28046; Thu, 16 Aug 2001 16:45:04 +0400 Date: Thu, 16 Aug 2001 16:45:04 +0400 (MSD) From: Vitaly Lugovsky To: David Mentre cc: Subject: Re: [Caml-list] Segfault in a native code multi-threaded program In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk On 16 Aug 2001, David Mentre wrote: > Hello dear Camlers, > > My multi-threaded program works well with the byte code compiler but > (sometimes) produces a segfault with the native code compiler. How can I > have more info to find the specific line of code that produces this > segfault? I've tried to run gdb but even when the program works until > its end, gdb is blocked. You can try gdb -c core after segfault even in multithreaded environment. And, sure, you can use assertions and debugging output (do not forget to flush it) to find out where the shit happens. ------------------- Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr