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 SAA15514; Thu, 18 Sep 2003 18:23:06 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id SAA16402 for ; Thu, 18 Sep 2003 18:23:05 +0200 (MET DST) X-SPAM-Warning: Sending machine is listed in blackholes.five-ten-sg.com Received: from vsmtp2.tin.it (vsmtp2.tin.it [212.216.176.222]) by concorde.inria.fr (8.11.1/8.11.1) with ESMTP id h8IGN4j01754 for ; Thu, 18 Sep 2003 18:23:04 +0200 (MET DST) Received: from dalamar.takhisis.org (80.117.63.206) by vsmtp2.tin.it (7.0.019) id 3F4F193C008C8254 for caml-list@inria.fr; Thu, 18 Sep 2003 18:23:03 +0200 Received: from fistandantilus.takhisis.org (fistandantilus.takhisis.org [192.168.1.113]) by dalamar.takhisis.org (Postfix) with ESMTP id F1E31B79C for ; Thu, 18 Sep 2003 18:23:02 +0200 (CEST) Received: by fistandantilus.takhisis.org (Postfix, from userid 3148) id 651D227420D; Thu, 18 Sep 2003 18:23:01 +0200 (CEST) Date: Thu, 18 Sep 2003 18:23:01 +0200 From: Stefano Zacchiroli To: Ocaml Subject: Re: [Caml-list] Segmentation fault at process initialization Message-ID: <20030918162301.GA872@fistandantilus.takhisis.org> Mail-Followup-To: Ocaml References: <3F69A471.9020807@baretta.com> <20030918125254.GA22780@redhat.com> <3F69B143.3080104@baretta.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F69B143.3080104@baretta.com> User-Agent: Mutt/1.5.4i X-Loop: caml-list@inria.fr X-Spam: no; 0.00; bononia:01 caml-list:01 baretta:01 gdb:01 ocamlc:01 crashes:01 crashes:01 gdb:01 backtraces:01 invocations:01 bononia:01 alex:01 bytecode:01 bytecode:01 toplevel:01 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk On Thu, Sep 18, 2003 at 03:21:07PM +0200, Alex Baretta wrote: > >If it's a native code version, try running it under gdb and look at > >the stack trace. You can usually work out from the name which module > >was being compiled. It'll be something like Module__entry for the > >toplevel code, or Module__function_123 for 'function' in the module. > Let me point out that it is not ocamlc which crashes, but it is my > bytecode executable which crashes immediately, before any of my code is > executed--otherwise I'd get some diagnostic output, which I do not get. You were not misunderstood. The suggestion of using gdb is still valid even if you're running bytecode executables, using gdb backtraces you will be able to see interesting stuff like external C functions invocations. Cheers. -- Stefano Zacchiroli -- Master in Computer Science @ Uni. Bologna, Italy zack@{cs.unibo.it,debian.org,bononia.it} - http://www.bononia.it/zack/ " I know you believe you understood what you think I said, but I am not sure you realize that what you heard is not what I meant! " -- G.Romney ------------------- To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ Beginner's list: http://groups.yahoo.com/group/ocaml_beginners