From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: David Fox <dsfox@cogsci.ucsd.edu>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Seg fault with -custom and 2049 lets...
Date: Tue, 17 Apr 2001 17:04:19 +0200 [thread overview]
Message-ID: <20010417170419.A19256@pauillac.inria.fr> (raw)
In-Reply-To: <lu4rvu9dhz.fsf_-_@hci.ucsd.edu>; from dsfox@cogsci.ucsd.edu on Thu, Apr 12, 2001 at 11:31:04AM -0700
> If I create a program with 2049 simple functions:
> I get a seg fault if I compile it with the -custom flag and use a
> debugging version of malloc:
> or if I link using the debugging library libcamlrund.a:
Yes, this is a bug in the bytecode compiler causing the virtual
machine not to grow its stack enough to accommodate all the stack
slots that your declaration requires. This will be fixed shortly.
- Xavier Leroy
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-04-17 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-12 18:31 David Fox
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 ` Xavier Leroy [this message]
2001-04-18 23:36 ` [Caml-list] Seg fault with -custom and 2049 lets 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=20010417170419.A19256@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=dsfox@cogsci.ucsd.edu \
/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