From: Pierre Weis <pierre.weis@inria.fr>
To: alex@baretta.com (Alex Baretta)
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Segmentation fault at process initialization
Date: Thu, 18 Sep 2003 15:44:18 +0200 (MET DST) [thread overview]
Message-ID: <200309181344.PAA12993@pauillac.inria.fr> (raw)
In-Reply-To: <3F69B143.3080104@baretta.com> from Alex Baretta at "Sep 18, 103 03:21:07 pm"
Hi Alex,
> Richard Jones wrote:
> >
> > Obviously under no circumstances, but I've had it happen a few times.
>
> Not really. Ocaml programs are guaranteed to be segmetation fault free
> only unless they link to C code or use the Marshal module to input data
> structures.
Or you use the Obj module, or you do a stack overflow on some
architectures, or you access out of a string or array on some others.
[...]
Anyhow, if it is possible, try to compile your code with the bytecode
compiler and use the debugger that easily find this kind of problems.
Another simple way to localize the problem is to add a message at the
end of each compilation unit; for instance, as last line of the
implementation file foo.ml of module Foo, just write:
prerr_endline "Module Foo successfully initialized.";;
This way, you could normally see which module fails to initialized and
then you could find more easily why.
Hope this helps,
Pierre Weis
INRIA, Projet Cristal, Pierre.Weis@inria.fr, http://pauillac.inria.fr/~weis/
-------------------
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
next prev parent reply other threads:[~2003-09-18 13:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 12:26 Alex Baretta
2003-09-18 12:52 ` Richard Jones
2003-09-18 13:21 ` Alex Baretta
2003-09-18 13:44 ` Pierre Weis [this message]
2003-09-22 17:09 ` Alessandro Baretta
2003-09-22 18:47 ` Richard Jones
2003-09-22 20:57 ` Gerd Stolpmann
2003-09-18 16:23 ` Stefano Zacchiroli
2003-09-18 16:54 ` Damien Doligez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200309181344.PAA12993@pauillac.inria.fr \
--to=pierre.weis@inria.fr \
--cc=alex@baretta.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox