caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Mark Shinwell" <mshinwell@janestcapital.com>
To: Raj Bandyopadhyay <rajb@rice.edu>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Segfault in Garbage collector code: any ideas?
Date: Thu, 19 Jun 2008 17:51:31 -0400	[thread overview]
Message-ID: <20080619215131.GM30596@janestcapital.com> (raw)
In-Reply-To: <D94E4621-B7D4-43A3-BD08-0352A32F2122@rice.edu>

On Thu, Jun 19, 2008 at 04:45:27PM -0500, Raj Bandyopadhyay wrote:
> 1) From past  experience, this  sort  of  thing seems  to  occur when  
> I forget to use a CAMLparam/local/return  macro somewhere. However, I  
> have looked over my C code several times and can't find any such  
> problem. Is there any other scenario where this sort of segfault can  
> occur?

One thing worth checking is that you've used a Store_field statement
rather than attempting to use Field (...) as an lvalue.  The latter is
often unsafe (see Rule 6 of "Low-level interface" in the Interfacing C
chapter of the manual).

Mark


      reply	other threads:[~2008-06-19 21:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 21:45 Raj Bandyopadhyay
2008-06-19 21:51 ` Mark Shinwell [this message]

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=20080619215131.GM30596@janestcapital.com \
    --to=mshinwell@janestcapital.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=rajb@rice.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;
as well as URLs for NNTP newsgroup(s).