caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Robert Roessler <roessler@rftp.com>
To: Caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Missing overflow exception message in ocamlopt
Date: Wed, 11 Oct 2006 18:04:27 -0700	[thread overview]
Message-ID: <452D949B.2030503@rftp.com> (raw)
In-Reply-To: <43CD2D195487A448934920501C6EDB23026B23C3@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>

Jakob Lichtenberg wrote:
> Is this a bug in ocamlopt?

No - rather, it is the ugly intrusion of reality. ;)

As has been already pointed out, it isn't easy to generate code that 
detects this at runtime under a widely varying set of environments and 
conditions... to tighten it up further would likely start costing in 
performance (and what is ocamlopt for?).

A related veiwpoint says that while you still don't understand your 
app's logic and control paths well enough to predict/avoid things like 
runaway stack usage - you use the interpreted version.  THEN you 
switch to the ocamlopt version when you think you are ready (and be 
prepared to switch back if you are proven wrong).

> On Wednesday 11 October 2006 19:46, Jakob Lichtenberg wrote:
>> When I compile the following program as byte code I see a stack
> overflow
>> (expected).  When using ocamlopt it seems that the program dies and I
> do
>> not see the expected overflow exception?
> 
> OCaml doesn't always throw the Stack_overflow exception from native
> code. On 
> some systems it seg faults.

Robert Roessler
roessler@rftp.com
http://www.rftp.com


  reply	other threads:[~2006-10-12  1:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-11 18:46 Jakob Lichtenberg
2006-10-11 19:03 ` [Caml-list] " Jon Harrop
2006-10-11 19:17   ` Richard Jones
2006-10-11 19:25     ` Gerd Stolpmann
2006-10-11 20:26     ` Jon Harrop
2006-10-11 19:45   ` Jakob Lichtenberg
2006-10-12  1:04     ` Robert Roessler [this message]
2006-10-15 15:58 ` Xavier Leroy
2006-10-16  3:50   ` Jakob Lichtenberg

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=452D949B.2030503@rftp.com \
    --to=roessler@rftp.com \
    --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;
as well as URLs for NNTP newsgroup(s).