From: Francois Berenger <francois.berenger@inria.fr>
To: OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Marshall.from_channel and segmentation fault
Date: Fri, 12 Jun 2015 10:38:13 +0200 [thread overview]
Message-ID: <557A9A75.9040307@inria.fr> (raw)
In-Reply-To: <20150612052738.GA3684@pllab.is.ocha.ac.jp>
On 06/12/2015 07:27 AM, Kenichi Asai wrote:
> The OCaml manual for the Marshall module says:
>
>> (Marshal.from_channel chan : type). Anything can happen at run-time
>> if the object in the file does not belong to the given type.
>
> and this "Anything" contains segmentation fault. Is it difficult to
> avoid this segmentation fault and, e.g., raise an exception instead?
Maybe bin_prot from janestreet is better for your use case.
I think it will throw an exception if you try to unmarshal something
of the wrong type.
> Sincerely,
>
--
Regards,
Francois.
"When in doubt, use more types"
prev parent reply other threads:[~2015-06-12 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 5:27 Kenichi Asai
2015-06-12 7:39 ` Romain Bardou
2015-06-12 8:26 ` Kenichi Asai
2015-06-12 8:55 ` Romain Bardou
2015-06-12 8:41 ` Francois Berenger
2015-06-12 8:38 ` Francois Berenger [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=557A9A75.9040307@inria.fr \
--to=francois.berenger@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).