From: Jamie Brandon <jamie@scattered-thoughts.net>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Causes for segfaults
Date: Thu, 4 Nov 2010 20:39:27 +0000 [thread overview]
Message-ID: <AANLkTim_gzPoE_+xcFWveDo_bRRn00hsff3JGqk4w9Dy@mail.gmail.com> (raw)
In-Reply-To: <201011042125.38754.raphlalou@gmail.com>
I'm not using Obj. I am unmarshalling. I have 'ulimit -s unlimited'
set and I'm unmarshalling with the exact same binary that did the
marshalling. The unmarshalling itself finishes ok but I guess the
segfault could be caused when accessing the resulting data structure?
I'm marshalling data which contains a DynArray which in turn contains
functional values, but I'm using [Marshal.No_sharing;
Marshal.Closures] and I haven't changed the code between marshalling
and unmarshalling.
On Thu, Nov 4, 2010 at 8:25 PM, Raphael Proust <raphlalou@gmail.com> wrote:
> Le jeudi 04 novembre 2010 21:19:33, Jamie Brandon a écrit :
>> Is there an authoritative list anywhere of the possible causes for
>> segfaults in ocaml? I'm not using the FFI or -unsafe and I have ruled
>> out overflowing the c stack and allocating large strings/arrays. I'm
>> using ocaml 3.09.3 with extlib, netclient, json-static, xml-light, str
>> and no compilation options.
>
> Unmarshalling can cause segfaults and Obj.magic too.
>
> --
> _______
> Raphaël
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
next prev parent reply other threads:[~2010-11-04 20:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 20:19 Jamie Brandon
2010-11-04 20:25 ` [Caml-list] " Raphael Proust
2010-11-04 20:39 ` Jamie Brandon [this message]
2010-11-05 15:54 ` David MENTRE
2010-11-05 22:18 ` oliver
2010-11-04 20:41 ` Till Varoquaux
2010-11-05 23:14 ` Jamie Brandon
[not found] ` <384325291.294734.1288998871132.JavaMail.root@zmbs3.inria.fr>
2010-11-06 2:51 ` Daniel de Rauglaudre
2010-11-08 14:26 ` Jamie Brandon
2010-11-08 14:48 ` Till Varoquaux
2010-11-10 15:52 ` Jamie Brandon
2010-11-15 17:58 ` Jamie Brandon
2010-11-15 18:17 ` John Whitington
2010-11-15 18:38 ` Jamie Brandon
2010-11-15 21:47 ` Török Edwin
[not found] ` <157788745.568057.1289846305435.JavaMail.root@zmbs3.inria.fr>
2010-11-15 18:50 ` Daniel de Rauglaudre
2010-11-15 19:00 ` Anil Madhavapeddy
2010-11-15 19:08 ` Norman Hardy
[not found] ` <1795362267.568432.1289847605872.JavaMail.root@zmbs3.inria.fr>
2010-11-15 19:21 ` Daniel de Rauglaudre
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=AANLkTim_gzPoE_+xcFWveDo_bRRn00hsff3JGqk4w9Dy@mail.gmail.com \
--to=jamie@scattered-thoughts.net \
--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).