caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml+spacetime crashes during camlp5 compilation
Date: Sun, 19 Feb 2017 04:00:10 +0100	[thread overview]
Message-ID: <20170219030010.GA1754@yquem.inria.fr> (raw)
In-Reply-To: <1487451144.4182.85.camel@gerd-stolpmann.de>

Hi,

On Sat, Feb 18, 2017 at 09:52:24PM +0100, Gerd Stolpmann wrote:

> print: ulimit -s (or just ulimit -a). This is in kilobytes.
> Change: e.g. ulimit -s 16384 to set it to 16MB.

By setting my ulimit to 1024 (ulimit -s 1024, the default being 8192
in my computer), I managed to indeed repeat the error: I get a Stack
Overflow error while compiling q_MLast.ml.

But trying to split the big EXTEND statement into three parts, the
bug remains. Perhaps it is due to the global size of the file? I
don't know.

It would be interesting if the OCaml team (if you read this message)
could tell us the reason of this Stack Overflow inside OCaml and what
to change in my file to prevent it.

-- 
Daniel de Rauglaudre
http://pauillac.inria.fr/~ddr/

  parent reply	other threads:[~2017-02-19  3:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 22:00 Kakadu
2017-02-18  1:53 ` Daniel de Rauglaudre
2017-02-18  1:58   ` Gabriel Scherer
2017-02-18  7:39     ` Kakadu
2017-02-18  8:49       ` Leo White
2017-02-18 10:31         ` Daniel de Rauglaudre
2017-02-18 11:17           ` Kakadu
2017-02-18 20:52           ` Gerd Stolpmann
2017-02-18 21:02             ` Kakadu
2017-02-18 21:14               ` Kakadu
2017-02-19  3:00             ` Daniel de Rauglaudre [this message]
2017-02-19  7:34               ` Kakadu
2017-02-19  8:43                 ` Daniel de Rauglaudre

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=20170219030010.GA1754@yquem.inria.fr \
    --to=daniel.de_rauglaudre@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).