From: "Paul A. Steckler" <steck@stecksoft.com>
To: Ocaml Mailing List <caml-list@inria.fr>
Subject: [Caml-list] ocamlopt segfault on large static array
Date: Mon, 14 Jan 2019 11:05:52 -0800 [thread overview]
Message-ID: <CAMSKV5dp+DdAjT_t++6maEv7LeHRS6EGye7h5sp8bmjarDag=g@mail.gmail.com> (raw)
In my OCaml program, I have a large static 2D array, where the inner
array contains pairs of strings. The inner arrays each have 2**9
elements, the outer array has about 1700 elements.
The strings are about 90 characters each.
If I compile it with ocamlc 4.07.0, everything is fine. With ocamlopt,
I get a segfault.
What limit am I hitting to get the segfault?
-- Paul
--
Caml-list mailing list. Subscription management and archives:
https://sympa.inria.fr/sympa/arc/caml-list https://inbox.ocaml.org/caml-list
Forum: https://discuss.ocaml.org/
Bug reports: http://caml.inria.fr/bin/caml-bugs
next reply other threads:[~2019-01-14 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 19:05 Paul A. Steckler [this message]
2019-01-14 19:28 ` Viet Le
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='CAMSKV5dp+DdAjT_t++6maEv7LeHRS6EGye7h5sp8bmjarDag=g@mail.gmail.com' \
--to=steck@stecksoft.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;
as well as URLs for NNTP newsgroup(s).