From: Peng Zang <peng.zang@gmail.com>
To: caml-list@yquem.inria.fr
Subject: strange behavior with camlp4 and #use
Date: Tue, 16 Sep 2008 17:31:37 -0400 [thread overview]
Message-ID: <200809161731.40062.peng.zang@gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I am running 3.10.2 installed from GODI. Findlib is similarly installed. I
run into the following error
"I/O error: Bad file descriptor"
when I try to '#use somefile' several times (when camlp4 is turned on).
I can reproduce this weird behavior as follows:
Objective Caml version 3.10.2
# #use "topfind";;
# #camlp4o;;
# #use "foo.ml";;
- : int = 1
# #use "foo.ml";;
- : int = 1
# #use "foo.ml";;
I/O error: Bad file descriptor
Does anyone else get this weird behavior? Why would it fail on the later
times? Was a file descriptor left unclosed? Is this a bug?
Peng
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
iD8DBQFI0CW8fIRcEFL/JewRAnD+AKDJo65H/y8oeT+ByCrQg8S2ZBHrhQCff+DD
wF9xbAA90UTcMjW/vJvAy/U=
=+e8p
-----END PGP SIGNATURE-----
next reply other threads:[~2008-09-16 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 21:31 Peng Zang [this message]
2008-09-16 21:58 ` [Caml-list] " Hezekiah M. Carty
2008-09-16 23:58 ` Peng Zang
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=200809161731.40062.peng.zang@gmail.com \
--to=peng.zang@gmail.com \
--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).