caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David Fox <dsfox@cogsci.ucsd.edu>
To: caml-list@inria.fr
Subject: [Caml-list] Seg fault with -custom and 2049 lets...
Date: 12 Apr 2001 11:31:04 -0700	[thread overview]
Message-ID: <lu4rvu9dhz.fsf_-_@hci.ucsd.edu> (raw)
In-Reply-To: William Chesters's message of "Thu, 12 Apr 2001 19:53:45 +0200 (CEST)"

If I create a program with 2049 simple functions:

  let f1 () = ()
  let f2 () = ()
  ...
  let f2049 () = ()

(You can build this using yes "" | cat -n | head -2049 |
 sed 's/^[^0-9]*\([0-9]*\)[^0-9]*$/let f\1 () = ()/' > y.ml)

I get a seg fault if I compile it with the -custom flag and use a
debugging version of malloc:

  % ocamlc -custom y.ml -ccopt -lefence
  % ./a.out
  
   Electric Fence 2.2.0 Copyright (C) 1987-1999 Bruce Perens <bruce@perens.com>
  Segmentation fault (core dumped)
  % 

or if I link using the debugging library libcamlrund.a:

  % ./a.out
  ### O'Caml runtime: debug mode ###
  Initial minor heap size: 128k bytes
  Initial major heap size: 248k bytes
  Initial space overhead: 42%
  Initial max overhead: 1000000%
  Initial heap increment: 248k bytes
  Initial stack limit: 1024k bytes
  file interp.c; line 255 ### Assertion failed: sp >= stack_low

If I use the regular (non-debugging) library I don't get the seg fault
immediately, but in a real life situation things get ugly pretty
quickly.

-david
-------------------
To unsubscribe, mail caml-list-request@inria.fr.  Archives: http://caml.inria.fr


             reply	other threads:[~2001-04-12 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-12 18:31 David Fox [this message]
2001-04-13 14:01 ` David Fox
2001-04-14 10:40 ` [Caml-list] Just wasted half-an-hour on returned curried functions Mattias Waldau
2001-04-17 15:04 ` [Caml-list] Seg fault with -custom and 2049 lets Xavier Leroy
2001-04-18 23:36   ` David Fox

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=lu4rvu9dhz.fsf_-_@hci.ucsd.edu \
    --to=dsfox@cogsci.ucsd.edu \
    --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).