caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alex Baretta <alex@baretta.com>
To: "Eric C. Cooper" <ecc@cmu.edu>, ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Troubles with marshaled/unmarshaled exception
Date: Thu, 04 Dec 2003 20:05:17 +0100	[thread overview]
Message-ID: <3FCF856D.5060101@baretta.com> (raw)
In-Reply-To: <20031204185113.GB10706@localhost>

Eric C. Cooper wrote:
> On Thu, Dec 04, 2003 at 07:11:51PM +0100, Alex Baretta wrote:

> But something is indeed broken.  Here's a slight variant of the above:
> 
>         Objective Caml version 3.07+2
> 
> # let e = Failure "test";;
> val e : exn = Failure "test"
> # let e' = Failure "test";;
> val e' : exn = Failure "test"
> # let e'' =  Marshal.from_string (Marshal.to_string e []) 0;;
> val e'' : 'a = <poly>
> # e'' ^ "good-bye";;
> Segmentation fault
> 

There's nothing wrong here. Module Marshal is not type safe. If you use 
it incorrectly you cannot complain if your program segfaults. The value 
represented by e'' actually has type exn, however the compiler cannot 
know this because you are defining it through Marshal.from_xxxx, which 
is not type safe. This allows you to type-check e'' ^ "good-bye" which 
segfaults.

Alex

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2003-12-04 19:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04 15:46 Artem Prisyznuk
2003-12-04 18:11 ` Alex Baretta
2003-12-04 18:51   ` Eric C. Cooper
2003-12-04 19:05     ` Alex Baretta [this message]
2003-12-04 19:50       ` Eric C. Cooper
2003-12-04 19:14   ` Artem Prisyznuk
2003-12-05  0:14 ` Jason Hickey
2003-12-05  7:31   ` Artem Prisyznuk

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=3FCF856D.5060101@baretta.com \
    --to=alex@baretta.com \
    --cc=caml-list@inria.fr \
    --cc=ecc@cmu.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).