From: Bruno.Verlyck@inria.fr
To: jgoerzen@complete.org
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Cash broken?
Date: Fri, 28 May 2004 15:52:23 +0200 [thread overview]
Message-ID: <200405281352.i4SDqNnI031885@waco.inria.fr> (raw)
In-Reply-To: <20040528131339.GC9268@excelhustler.com> (jgoerzen@complete.org)
Date: Fri, 28 May 2004 08:13:39 -0500
From: John Goerzen <jgoerzen@complete.org>
On Fri, May 28, 2004 at 12:26:15PM +0200, Bruno.Verlyck@inria.fr wrote:
> # open Cash;;
> # run_with_strings (fun () -> exec_path "ls" []);;
> Exception: Sys_error "Bad file descriptor".
> # Exception: Sys_error "Bad file descriptor".
> Ideas? (Cash 0.20)
> Would you mind sending me more OS details ? A backtrace would be
> very useful, and/or the result of trace/truss/strace -f ?
This is on Debian sid, Linux 2.6.6. I couldn't figure out how to
get a backtrace. However, from the forked child, I see:
[pid 9461] close(4) = 0
[pid 9461] close(4) = -1 EBADF (Bad file descriptor)
(Full strace attached)
Thank you. It confirms my first guess.
Will try the patch. How does the CVS version rank in terms of
stability?
Pretty good :-). The only risk is that I converted all the sources to
use Cstr/String13, and I have to admit I introduced some translation
errors. I fixed those I found, but it could be that there's still
`just one more bug'. I would be very interested if you (or anyone
else) find it out, or tell me everything you tried is OK.
Thanks anyway,
Bruno.
-------------------
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
prev parent reply other threads:[~2004-05-28 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 19:38 John Goerzen
2004-05-28 10:26 ` Bruno.Verlyck
2004-05-28 13:13 ` John Goerzen
2004-05-28 13:52 ` Bruno.Verlyck [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=200405281352.i4SDqNnI031885@waco.inria.fr \
--to=bruno.verlyck@inria.fr \
--cc=caml-list@inria.fr \
--cc=jgoerzen@complete.org \
/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).