From: Alex Baretta <alex@baretta.com>
To: Jacques Garrigue <caml-bugs@pauillac.inria.fr>,
Ocaml <caml-list@inria.fr>
Subject: [Caml-list] Segmentation fault at process initialization
Date: Thu, 18 Sep 2003 14:26:25 +0200 [thread overview]
Message-ID: <3F69A471.9020807@baretta.com> (raw)
When the Xcaml runtime system is linked with the -linkall option of
ocamlc-3.06, the xcaml executable I get crashes with a segmentation
fault at process initialization. If, on the other hand, I link the
executable without the -linkall option, it runs fine, except for the
fact that it lacks several library modules it should have.
The libraries I'm using are the following:
postgres, which is know to work very well;
cgi, which contains no C code;
and str, num and dynlink coming straight from the ocaml distribution.
My code is definitely not a problem because it runs fine if the -linkall
option is suppressed. Neither is the -linkall option a problem in and of
itself, because I can reproduce the behaviour by issuing equivalent
linking commands using the cmo files as opposed the cmas.
How can I diagnose this segmentation fault? Under what circumstances
exactly are ocaml programs "allowed" to crash with a segmentation fault?
Alex
-------------------
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 reply other threads:[~2003-09-18 12:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 12:26 Alex Baretta [this message]
2003-09-18 12:52 ` Richard Jones
2003-09-18 13:21 ` Alex Baretta
2003-09-18 13:44 ` Pierre Weis
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=3F69A471.9020807@baretta.com \
--to=alex@baretta.com \
--cc=caml-bugs@pauillac.inria.fr \
--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;
as well as URLs for NNTP newsgroup(s).