From: "Kevin S. Millikin" <kmillikin@atcorp.com>
To: "'Oleg Trott'" <oleg_trott@columbia.edu>,
David Brown <caml-list@davidb.org>,
"Beck01, Wolfgang" <BeckW@t-systems.com>
Cc: "edahlman@atcorp.com" <edahlman@atcorp.com>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] Segmentation Fault on #load
Date: Tue, 28 Oct 2003 13:56:41 -0600 [thread overview]
Message-ID: <01C39D5B.513CCDF0.kmillikin@atcorp.com> (raw)
On Tuesday, October 28, 2003 1:38 PM, Oleg Trott
[SMTP:oleg_trott@columbia.edu] wrote:
> Technically, it's possible for "#load" to cause seg-fault if
"pretty" uses
> FFI and there is a bug somewhere. Otherwise, there may be a problem
> with Eric's copy of OCaml.
"pretty" is the pretty printer from George Necula's CIL. It does not
contain foreign code, but does call Obj.magic.
It appears to work for me (Ocaml 3.07 compiled with cygwin), but not
for Eric (Ocaml 3.07+2, cygwin).
----
Kevin S. Millikin Architecture Technology Corporation
Research Scientist Specialists in Computer Architecture
(952)829-5864 x162 http://www.atcorp.com
-------------------
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-10-28 19:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 19:56 Kevin S. Millikin [this message]
2003-10-28 21:37 ` Eric Dahlman
2003-10-31 19:05 ` [Caml-list] 3.07+2 lossage (was: Segmentation Fault on #load) Eric Dahlman
-- strict thread matches above, loose matches on Subject: below --
2003-10-29 8:20 [Caml-list] Segmentation Fault on #load Beck01, Wolfgang
2003-10-28 15:47 Beck01, Wolfgang
2003-10-28 9:05 ` David Brown
2003-10-28 19:37 ` Oleg Trott
2003-10-28 16:11 ` Stefano Zacchiroli
2003-10-27 19:23 Eric Dahlman
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=01C39D5B.513CCDF0.kmillikin@atcorp.com \
--to=kmillikin@atcorp.com \
--cc=BeckW@t-systems.com \
--cc=caml-list@davidb.org \
--cc=caml-list@inria.fr \
--cc=edahlman@atcorp.com \
--cc=oleg_trott@columbia.edu \
/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).