From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Arlen Cuss <celtic@sairyx.org>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Unix.Unix_error(31, "write", "") raised from format.ml!? This is not right.
Date: Tue, 08 Mar 2011 15:35:58 +0100 [thread overview]
Message-ID: <1299594958.30035.104.camel@thinkpad> (raw)
In-Reply-To: <1299550636.21350.49.camel@azayaka>
Am Dienstag, den 08.03.2011, 13:17 +1100 schrieb Arlen Cuss:
> Exception Unix.Unix_error(31, "write", "") occurred
> Exception Unix.Unix_error(56, "write", "") occurred
>
> Both are occurring with the same reported backtrace; the former is Unix
> error EMLINK (too many links), the latter EISCONN (socket is connected);
> the strange thing is that *neither* of these errors should be throwable
> on a write() call!
That's not quite correct.
Error 31 is EPIPE. Error 56 is ECONNRESET. You can easily find out by
typing in the toploop:
# (Obj.magic 31: Unix.error);;
- : Unix.error = Unix.EPIPE
# (Obj.magic 56: Unix.error);;
- : Unix.error = Unix.ECONNRESET
The error numbers are not the official Unix ones, but something that
ocaml uses internally.
Gerd
>
> I've ensured I'm correctly compiling with debug info, so I'm a bit lost.
> I can only assume a sprintf or similar call somewhere is going haywire.
>
> Anyone seen anything like this before?
>
> Best,
> Arlen
>
>
--
------------------------------------------------------------
Gerd Stolpmann, Bad Nauheimer Str.3, 64289 Darmstadt,Germany
gerd@gerd-stolpmann.de http://www.gerd-stolpmann.de
Phone: +49-6151-153855 Fax: +49-6151-997714
------------------------------------------------------------
next prev parent reply other threads:[~2011-03-08 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 2:17 Arlen Cuss
2011-03-08 2:22 ` Arlen Cuss
2011-03-08 14:35 ` Gerd Stolpmann [this message]
[not found] ` <1001695803.480327.1299594992792.JavaMail.root@zmbs4.inria.fr>
2011-03-08 21:28 ` Fabrice Le Fessant
2011-03-08 23:17 ` Gerd Stolpmann
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=1299594958.30035.104.camel@thinkpad \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=celtic@sairyx.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).