From: "Yaron M. Minsky" <yminsky@CS.Cornell.EDU>
To: "Caml List " <caml-list@inria.fr>
Subject: [Caml-list] Size limit on marshalling?
Date: Wed, 15 Jan 2003 16:25:49 -0500 (EST) [thread overview]
Message-ID: <29027.141.155.88.179.1042665949.squirrel@minsky-primus.homeip.net> (raw)
I've been getting some fairly inexplicable crashes on marshalling and
unmarshalling values, and I'm wondering if anyone has an idea why. Here's
a code snippet that will crash my copy of ocaml.
First, I create a pointlessly large array, and then save it to disk:
# let save_value fname value =
let file = open_out_bin fname in
output_value file value;
close_out file;;
val save_value : string -> 'a -> unit = <fun>
# let ar = Array.init (10000 * 256) (fun i -> String.copy "fooobar doobar");;
# save_value "/home/yminsky/foo.val" ar;;
The resulting file is 38400025 bytes long. Note that the length appears
to be critical. If you replace "fooobar doobar' with "foobar doobar", the
problem goes away.
At this point, I start a new session of ocaml and reload the value, and
then ensure that it is garbage collected. That's when I get the segfault.
# let ar = (get_value "foo.val" : string array);;
# let ar = ();;
# Gc.compact ();;
And that's when I get the segfault. So, any thoughts? Is this a bug? Or
just some unspoken limit of the compiler? This is a dummy example, but
this is a real limit I'm running up against in my code.
Yaron
--
|--------/ Yaron M. Minsky \--------|
|--------\ http://www.cs.cornell.edu/home/yminsky/ /--------|
Open PGP --- KeyID B1FFD916 (new key as of Dec 4th)
Fingerprint: 5BF6 83E1 0CE3 1043 95D8 F8D5 9F12 B3A9 B1FF D916
-------------------
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-01-15 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 21:25 Yaron M. Minsky [this message]
2003-01-16 13:15 ` 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=29027.141.155.88.179.1042665949.squirrel@minsky-primus.homeip.net \
--to=yminsky@cs.cornell.edu \
--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).