From: David MENTRE <dmentre@linux-france.org>
To: Jamie Brandon <jamie@scattered-thoughts.net>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Causes for segfaults
Date: Fri, 5 Nov 2010 16:54:37 +0100 [thread overview]
Message-ID: <AANLkTikkYBHuBD573uzSWf=pfRAHCtW=rkDs_kV+tu7E@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim_gzPoE_+xcFWveDo_bRRn00hsff3JGqk4w9Dy@mail.gmail.com>
Hello,
2010/11/4 Jamie Brandon <jamie@scattered-thoughts.net>:
> The unmarshalling itself finishes ok but I guess the
> segfault could be caused when accessing the resulting data structure?
You could frequently call major collection in the GC, in order to be
as close as possible to the source of the segfault (e.g. after your
unmarshalling).
Sincerely yours,
david
next prev parent reply other threads:[~2010-11-05 15:55 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
2010-11-05 15:54 ` David MENTRE [this message]
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='AANLkTikkYBHuBD573uzSWf=pfRAHCtW=rkDs_kV+tu7E@mail.gmail.com' \
--to=dmentre@linux-france.org \
--cc=caml-list@yquem.inria.fr \
--cc=jamie@scattered-thoughts.net \
/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).