From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>, caml-list@inria.fr
Subject: Re: [Caml-list] OCaml+spacetime crashes during camlp5 compilation
Date: Sat, 18 Feb 2017 21:52:24 +0100 [thread overview]
Message-ID: <1487451144.4182.85.camel@gerd-stolpmann.de> (raw)
In-Reply-To: <20170218103154.GA5070@yquem.inria.fr>
[-- Attachment #1: Type: text/plain, Size: 1692 bytes --]
Am Samstag, den 18.02.2017, 11:31 +0100 schrieb Daniel de Rauglaudre:
> On Sat, Feb 18, 2017 at 08:49:12AM +0000, Leo White wrote:
>
> >
> > As Gabriel said, it is probably just camlp5 being expensive to
> > compile
> > and spacetime tipping it over the edge. Have you tried increasing
> > the
> > stack size limit?
> Hmmm... perhaps I could test this bug by decreasing my stack size
> limit on my computer?
>
> The example given seems to show a problem with the file
> meta/q_MLast.ml which indeed contains a statement EXTEND which
> generates a rather long OCaml expression. Strange that this problem
> does not occur with ocaml_src/meta/q_MLast.ml which is a pretty
> printed version of the same file (for Camlp5 cold stard).
>
> I could try to split this EXTEND into several parts to make OCaml
> not having to use so much memory?
>
> BTW, how to show one's stack size limit (Linux) and change it?
print: ulimit -s (or just ulimit -a). This is in kilobytes.
Change: e.g. ulimit -s 16384 to set it to 16MB.
Note that there is a soft and a hard limit, and you cannot increase the
soft limit (which is the effective one) beyond the hard limit. Print
the hard limit with "ulimit -H -s". Root can also increase the hard
limit, however there's sometimes a per-architecture kernel limit.
Gerd
--
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany gerd@gerd-stolpmann.de
My OCaml site: http://www.camlcity.org
Contact details: http://www.camlcity.org/contact.html
Company homepage: http://www.gerd-stolpmann.de
------------------------------------------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2017-02-18 20:52 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 [this message]
2017-02-18 21:02 ` Kakadu
2017-02-18 21:14 ` Kakadu
2017-02-19 3:00 ` Daniel de Rauglaudre
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=1487451144.4182.85.camel@gerd-stolpmann.de \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=daniel.de_rauglaudre@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