From: Igor Peshansky <pechtcha@cs.nyu.edu>
To: skaller <skaller@users.sourceforge.net>
Cc: caml-list@yquem.inria.fr, Rhythmic Fistman <rfistman@gmail.com>,
Emmanuel Onzon <emmanuel.onzon@ens-lyon.fr>
Subject: Re: [Caml-list] cywgin stack overflow
Date: Wed, 13 Jun 2007 09:44:44 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.63.0706130858580.23164@access1.cims.nyu.edu> (raw)
In-Reply-To: <1181738340.6135.6.camel@rosella.wigram>
On Wed, 13 Jun 2007, skaller wrote:
> On Wed, 2007-06-13 at 17:34 +1000, skaller wrote:
> > Hi, we've got a problem with an Ocaml native code program running under
> > Cygwin exiting without producing output or diagnostics. I think
> > Cygwin is running Ocaml 3.08. It was suggested
> > this was probably a stack overflow. The program is Dypgen GLR
> > parser generator, which is probably heavily recursive. It works
> > fine on my AMD64/Ubuntu Linux box, Ocaml 3.10-dev+25 or something.
> >
> > Does anyone know how to increase the stack size, or have any other
> > idea how to work around this problem? Or any idea if it could
> > be any other problem?
>
> Woops! I misdiagnosed the problem I think. I put -ccopts and
> dypgen runs fine .. however Ocamlopt.opt does not compile it
> the generated file ;(
>
> The file src/flx_parser.ml is generated by Dypgen, but ocamlopt.opt
> doesn't compile it, nor issue any diagnostic (not even returning
> with an error code). It just completes without generating a
> src/flx_parse.cmx file.
>
> Unfortunately, recompiling Ocaml on Cygwin isn't an option.
> Is there someone here maintaining the Cygwin port?
Yes. I am. But I haven't yet had a chance to build anything newer than
3.08.
> Any chance of 3.09 series Ocaml, and, with the native
> code compiler built with a larger stack?
I thought Ocaml had growable stacks... I must've been confused.
Besides, I'm planning to build a 3.10 series shortly -- is there really a
pressing need for 3.09?
> I've yet to try running with larger memory for Cygwin as
> suggested by Igor -- the ml file is quite large:
>
> 20555 92221 804093 src/flx_parse.ml
>
> src/flx_parse.cmx on amd64/Ubuntu is 83569 bytes.
>
> I also suppose I can try ocamlopt (sans .opt) or even
> ocamlc (ouch!).
Do try to increase the available memory -- the amount Cygwin allocates by
default is rather small (256M, I believe). Another possibility is to run
the compilation under strace to see why it exits.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
Freedom is just another word for "nothing left to lose"... -- Janis Joplin
next prev parent reply other threads:[~2007-06-13 13:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 7:34 skaller
2007-06-13 11:29 ` [Caml-list] " Igor Peshansky
2007-06-13 12:05 ` skaller
2007-06-13 12:39 ` skaller
2007-06-13 13:44 ` Igor Peshansky [this message]
2007-06-13 14:00 ` skaller
2007-06-13 14:16 ` skaller
2007-06-13 14:45 ` Igor Peshansky
2007-06-13 16:20 ` Xavier Leroy
2007-06-13 16:27 ` Alain Frisch
2007-06-13 17:08 ` Igor Peshansky
2007-06-13 17:12 ` Alain Frisch
2007-06-14 7:03 ` Olivier Andrieu
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=Pine.GSO.4.63.0706130858580.23164@access1.cims.nyu.edu \
--to=pechtcha@cs.nyu.edu \
--cc=caml-list@yquem.inria.fr \
--cc=emmanuel.onzon@ens-lyon.fr \
--cc=rfistman@gmail.com \
--cc=skaller@users.sourceforge.net \
/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