From: Damien Doligez <damien.doligez@inria.fr>
To: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Segfault using malloc within stubs
Date: Tue, 8 Feb 2005 18:51:47 +0100 [thread overview]
Message-ID: <1A8E9A39-79FA-11D9-BE0B-000D9345235C@inria.fr> (raw)
In-Reply-To: <42062429.4050404@noos.fr>
On Feb 6, 2005, at 15:05, julius wrote:
> Actually, this is just un exemple that illustrates the real function I
> used. We can add some use of the test pointer and result value but it
> changes nothing: in this function you can't do anything that someway
> malloc the test pointer.
> As you say it's very weird and much disapointing :)
Except for the "CAML" macro that doesn't exist and the uninitialized
value
of the "result" variable, your code is correct. The bug must be within
the part that you removed.
-- Damien
next prev parent reply other threads:[~2005-02-08 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 14:05 julius
2005-02-08 17:51 ` Damien Doligez [this message]
2005-02-08 18:42 ` art yerkes
2005-02-25 0:36 Garry Belka
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=1A8E9A39-79FA-11D9-BE0B-000D9345235C@inria.fr \
--to=damien.doligez@inria.fr \
--cc=caml-list@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).