caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Michael Hicks <mwh@cs.umd.edu>
To: "Yaron M. Minsky" <yminsky@CS.Cornell.EDU>,
	Ocaml List <caml-list@inria.fr>
Subject: RE: [Caml-list] Uncaught exceptions (or am I going crazy?)
Date: Wed, 02 Oct 2002 11:06:30 -0400	[thread overview]
Message-ID: <MCEJKGLFOBBOHDNADBNAOEPPCBAA.mwh@cs.umd.edu> (raw)
In-Reply-To: <3D9B03DF.5040806@cs.cornell.edu>

In Unix, if you don't create a signal handler that explicitly handles or
ignores the signal SIGPIPE, this signal will be thrown to the application if
its tries to write to a file descriptor that has been closed (in particular
if it has received an RST from the remote TCP host).  If the signal is dealt
with by the application, the offending write will return the error EPIPE.  I
presume that the OCaml implementation has manifested the throwing of the
signal by raising the exception you are seeing.

Hope this helps.
Mike

-----Original Message-----
From: owner-caml-list@pauillac.inria.fr
[mailto:owner-caml-list@pauillac.inria.fr]On Behalf Of Yaron M. Minsky
Sent: Wednesday, October 02, 2002 10:34 AM
To: Ocaml List
Subject: [Caml-list] Uncaught exceptions (or am I going crazy?)


I'm getting some very weird behavior with respect to exception handling
in ocaml 3.06.  I'm probably missing something obvious, but here's my
situation.  I have a networking application which for some reason,
occasionally prints out the following message:

Uncaught exception: Sys_error("Broken pipe")

What's so strange about this is that as far as I can tell, there is no
place in my code where I actually print out such errors.  In particular,
the text "Uncaught exception" doesn't appear anywhere in my code, and I
don't see any printfs that could be the cause either.  And weirdly, this
only seems to come up with byte-code compiled code.

So has anyone else seen something like this?

y

-------------------
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
-------------------
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


  parent reply	other threads:[~2002-10-03  7:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-02 14:34 Yaron M. Minsky
2002-10-02 14:59 ` Didier Le Botlan
2002-10-02 15:01 ` Maxence Guesdon
2002-10-02 15:06 ` Michael Hicks [this message]
     [not found] ` <3D9B0978.E4A5D96@beaune.inria.fr>
2002-10-02 15:38   ` Yaron M. Minsky
2002-10-02 16:04     ` Alessandro Baretta
2002-10-02 15:57       ` Yaron M. Minsky
     [not found]         ` <15771.6363.899204.33252@paille.inria.fr>
     [not found]           ` <3D9B198D.7020605@cs.cornell.edu>
     [not found]             ` <15771.6812.266404.848081@paille.inria.fr>
2002-10-02 16:19               ` Yaron M. Minsky
2002-10-03  0:46 Arturo Borquez

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=MCEJKGLFOBBOHDNADBNAOEPPCBAA.mwh@cs.umd.edu \
    --to=mwh@cs.umd.edu \
    --cc=caml-list@inria.fr \
    --cc=yminsky@CS.Cornell.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).