From: brogoff@speakeasy.net
To: Yang Shouxun <yangsx@fltrp.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] stack overflow
Date: Tue, 8 Apr 2003 19:19:48 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0304081914280.8801-100000@grace.speakeasy.net> (raw)
In-Reply-To: <200304091010.37547.yangsx@fltrp.com>
The most likely explanation is that you created a very large list, say of
length over 50_000, and tried to apply some non-tail-recursive operation to it,
perhaps even implicitly. There was a very recent thread on this topic.
The second explanation is that you wrote some (non-tail) recursive function
and it blew the stack.
If you switch to the bytecode compiler and run with stack trace, you'll find out
pretty quickly.
-- Brian
On Wed, 9 Apr 2003, Yang Shouxun wrote:
> Dear OCaml users,
>
> I've written a modified version of C4.5 program in OCaml. However, when the
> input is big, say over 50000, the program (native code on Debian) died for
> stack overflow. Otherwise, it runs as expected.
>
> Can anybody explain possible reasons causing stack overflow in OCaml?
>
> Thanks for your time!
> shouxun
>
> -------------------
> 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
>
-------------------
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-04-09 2:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 2:10 Yang Shouxun
2003-04-09 2:19 ` brogoff [this message]
2003-04-09 2:45 ` Yang Shouxun
2003-04-09 8:14 ` Markus Mottl
2003-04-09 9:23 ` Yang Shouxun
2003-04-09 11:34 ` Markus Mottl
2003-04-10 4:12 ` Parallel CPS? (was Re: [Caml-list] stack overflow) Yang Shouxun
2003-04-10 4:58 ` Mike Lin
2003-04-09 14:14 ` CPS folds " Neel Krishnaswami
2003-04-09 16:54 ` brogoff
2003-04-09 17:23 ` Mike Lin
2003-04-09 2:43 ` [Caml-list] stack overflow David Brown
[not found] ` <200304091034.45256.yangsx@fltrp.com>
[not found] ` <16019.34434.468479.586884@barrow.artisan.com>
2003-04-09 2:53 ` Yang Shouxun
2003-04-09 6:45 ` David Monniaux
2003-04-13 15:42 ` John Max Skaller
2006-03-31 20:44 Stack_overflow mulhern
2006-03-30 23:03 ` [Caml-list] Stack_overflow Jon Harrop
2006-03-31 21:38 ` Eric Cooper
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.LNX.4.44.0304081914280.8801-100000@grace.speakeasy.net \
--to=brogoff@speakeasy.net \
--cc=caml-list@inria.fr \
--cc=yangsx@fltrp.com \
/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