From: "M E Leypold @ labnet" <leypold@informatik.uni-tuebingen.de>
To: Franck Delaplace <delapla@lami.univ-evry.fr>
Cc: OCAML <caml-list@inria.fr>
Subject: [Caml-list] Problem with ocamlopt
Date: Mon, 11 Mar 2002 13:36:29 +0100 [thread overview]
Message-ID: <15500.42189.563370.819377@hod.void.org> (raw)
In-Reply-To: <3C8C620F.6080801@lami.univ-evry.fr>
Franck Delaplace writes:
>
> When I try to compile a program with ocamlopt,
> the following exception is raised
>
> Uncaught exception: Stack overflow
> PS: You will find attached the source code
When trying to read it, one of my brain modules threw an exception:
Stack overflow. :-)
Hi Franck,
Actually I only wrote to make that joke, but to be a bit more useful:
It might be that the constructs used by the code generator you used to
translate the FA definitions into ocaml nest somewhat too deeply, and
since the ocamlcompiler parses recursive descendend (i think) its
stack overflows at some point or other.
Suggestions:
* Try cutting down your FA, let's say to half as a test case and
compile it then. Does it overflow still? If no, try to make your
FA smaller and keep functionality.
* Report a problem/bug to the tagcc people and use ocamlc in the
meantime waiting for a bug fix. If things are like I suggest,
that is should be called a tagcc bug, since there is IMHO no
reason for FA execution to use nested constructs this way
(nesting too deeply).
Regards -- Markus
-------------------
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 prev parent reply other threads:[~2002-03-11 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-11 7:51 Franck Delaplace
2002-03-11 12:36 ` M E Leypold @ labnet [this message]
2002-03-12 7:30 ` Franck Delaplace
2002-03-12 9:12 ` Christopher Quinn
2004-09-20 19:27 Tyler Eaves
2004-09-22 15:16 ` Christophe TROESTLER
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=15500.42189.563370.819377@hod.void.org \
--to=leypold@informatik.uni-tuebingen.de \
--cc=caml-list@inria.fr \
--cc=delapla@lami.univ-evry.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