Re: [Caml-list] Segmentation fault at process initialization

[Stefano Zacchiroli <zack@bononia.it>]

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