From: Sean Seefried <sean.seefried@nicta.com.au>
To: caml-list@yquem.inria.fr
Subject: Heaps size problems with "caml_alloc_small" in foreign function interfaces
Date: Fri, 11 Jul 2008 18:21:51 +1000 [thread overview]
Message-ID: <DF8B3A72-8456-4441-8870-04856DEF4C5F@nicta.com.au> (raw)
Hi,
I'm having a problem where sometimes a call to "caml_alloc_small" from
C results in a segmentation fault. If I increase the size of the stack
using OCAMLRUNPARAM=s=1000k then I don't get the crash anymore. It
seems strange that I have to increase the size of the heap manually
like this. Is this because I'm calling this function from C?
If I want to increase the size of the heap in C how do I do this?
Could I write a "safe" caml_alloc_small which first checks to see if
there is enough memory and then increases the heap size if not?
Sean
next reply other threads:[~2008-07-11 8:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 8:21 Sean Seefried [this message]
2008-07-11 9:40 ` [Caml-list] " Richard Jones
2008-07-11 9:51 ` Richard Jones
2008-07-11 10:21 ` Sean Seefried
2008-07-11 15:56 ` Richard Jones
2008-07-11 14:11 ` Xavier Leroy
2008-07-12 3:20 ` Sean Seefried
2008-07-12 6:00 ` Sean Seefried
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=DF8B3A72-8456-4441-8870-04856DEF4C5F@nicta.com.au \
--to=sean.seefried@nicta.com.au \
--cc=caml-list@yquem.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).