From: Norman Ramsey <nr@eecs.harvard.edu>
To: Anil Madhavapeddy <anil@recoil.org>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] trouble with Marshal.to_string
Date: Sat, 08 Oct 2005 14:47:00 -0400 [thread overview]
Message-ID: <20051008184700.5CD712B2A62@labrador.eecs.harvard.edu> (raw)
In-Reply-To: <710BDF7D-A164-4655-975E-553017F62321@recoil.org>
> > 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,
Aha! It seems possible that a closure has captured an open file handle...
Norman
next prev parent reply other threads:[~2005-10-08 18:47 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
2005-10-08 18:47 ` Norman Ramsey [this message]
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=20051008184700.5CD712B2A62@labrador.eecs.harvard.edu \
--to=nr@eecs.harvard.edu \
--cc=anil@recoil.org \
--cc=caml-list@yquem.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).