caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anil Madhavapeddy <anil@recoil.org>
To: Norman Ramsey <nr@eecs.harvard.edu>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] trouble with Marshal.to_string
Date: Sat, 8 Oct 2005 17:57:40 +0100	[thread overview]
Message-ID: <710BDF7D-A164-4655-975E-553017F62321@recoil.org> (raw)
In-Reply-To: <20051008163518.B1B262B2A62@labrador.eecs.harvard.edu>

On 8 Oct 2005, at 17:35, Norman Ramsey wrote:

>> Are you using any C bindings which create custom blocks?  That error
>> occurs if your custom block does not define a serialization function
>> (documented here: http://caml.inria.fr/pub/docs/manual-ocaml/
>> manual032.html#s:custom).
>>
>
> Thanks; at least now I have some idea what's happening.
>
> I'm not aware of using any C bindings at all, although I am linking
> against the Unix library.  My final executable does contain
> definitions of caml_alloc_custom, caml_register_custom_operations, and
> related functions, but none of my .o or .a files refers to such a
> function.
>
> Any ideas how I might track down the source of a custom block?

The old-fashioned way, with grep :-)  I'm sure there are fancier  
ways, but...

shock:~/src/ocaml-3.08.4 avsm$ grep -r custom_serialize_def *
byterun/custom.c:  ops->serialize = custom_serialize_default;
byterun/custom.h:#define custom_serialize_default NULL
byterun/io.c:  custom_serialize_default,
otherlibs/graph/image.c:  custom_serialize_default,
otherlibs/systhreads/posix.c:  custom_serialize_default,
otherlibs/systhreads/posix.c:  custom_serialize_default,
otherlibs/systhreads/posix.c:  custom_serialize_default,
otherlibs/systhreads/win32.c:  custom_serialize_default,
otherlibs/systhreads/win32.c:  custom_serialize_default,
otherlibs/win32graph/draw.c:        custom_serialize_default,
otherlibs/win32unix/unixsupport.c:  custom_serialize_default,

So it looks like a few functions in the OCaml standard libraries  
aren't serializable; notable the systhreads.  Are you using threads  
in the structures you are marshalling?

Confirmed with a simple test:

let _ =
     let x = Thread.create (fun () -> ()) () in
     Marshal.to_string x [Marshal.Closures]

$ ocamlopt.opt -c -thread t.ml
$ ocamlopt.opt unix.cmxa threads.cmxa -thread -o t t.ml
$ ./t
Fatal error: exception Invalid_argument("output_value: abstract value  
(Custom)")

--
Anil Madhavapeddy                                 http://anil.recoil.org
University of Cambridge                          http://www.cl.cam.ac.uk


  reply	other threads:[~2005-10-08 16:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-08 15:34 Norman Ramsey
2005-10-08 16:09 ` [Caml-list] " Anil Madhavapeddy
2005-10-08 16:35   ` Norman Ramsey
2005-10-08 16:57     ` Anil Madhavapeddy [this message]
2005-10-08 18:47       ` Norman Ramsey
2005-10-08 18:59         ` Thomas Fischbacher

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=710BDF7D-A164-4655-975E-553017F62321@recoil.org \
    --to=anil@recoil.org \
    --cc=caml-list@yquem.inria.fr \
    --cc=nr@eecs.harvard.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).