From: Richard Jones <rich@annexia.org>
Cc: Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Ocamlc stack overflow
Date: Tue, 25 Nov 2003 14:06:14 +0000 [thread overview]
Message-ID: <20031125140614.GA5810@redhat.com> (raw)
In-Reply-To: <3FC356F5.9080309@baretta.com>
It's only 140 lines of code? Try chopping lines off the end of the
file until the thing compiles. Then you should be able to isolate
which statement causes the stack overflow. From there it should be a
simple enough job to either understand the problem and work around it,
or else come up with a minimal example which exhibits the bug.
Rich.
--
Richard Jones. http://www.annexia.org/ http://freshmeat.net/users/rwmj
Merjis Ltd. http://www.merjis.com/ - improving website return on investment
MONOLITH is an advanced framework for writing web applications in C, easier
than using Perl & Java, much faster and smaller, reusable widget-based arch,
database-backed, discussion, chat, calendaring:
http://www.annexia.org/freeware/monolith/
-------------------
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:[~2003-11-25 14:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 17:21 Alex Baretta
2003-11-24 17:47 ` Richard Jones
2003-11-25 13:19 ` Alex Baretta
2003-11-25 14:06 ` Richard Jones [this message]
2003-11-25 15:10 ` [Caml-list] Ocamlc stack overflow (Probably a typechecking bug) Alex Baretta
2003-11-25 17:50 ` [Caml-list] Ocamlc stack overflow Xavier Leroy
2003-11-24 18:22 ` Damien Doligez
2006-08-04 1:03 ocamlc Stack_overflow Denis Bueno
2006-08-09 2:00 ` Denis Bueno
2006-08-09 2:54 ` [Caml-list] " Jon Harrop
2006-08-09 4:19 ` Martin Jambon
2006-08-09 13:41 ` Denis Bueno
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=20031125140614.GA5810@redhat.com \
--to=rich@annexia.org \
--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