caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jeremie Dimino <jdimino@janestreet.com>
To: caml-list@inria.fr
Cc: ocsigen@inria.fr
Subject: Re: [Caml-list] BUG in unix.ml (was: strange errors when linking lwt.unix)
Date: Fri, 15 Mar 2013 11:38:06 +0000	[thread overview]
Message-ID: <CANhEzE5_OtOjxw5xAYd0S5pSwO906oXcXg=ZFu9+YnwGRLZ+Eg@mail.gmail.com> (raw)
In-Reply-To: <5142E780.7060806@hars.de>

On Fri, Mar 15, 2013 at 9:18 AM, Florian Hars <florian@hars.de> wrote:
> It probably escaped notice so far because only lwt_unix does enough strange
> things with signals in the default config to trigger it reliably.

Indeed.  BTW the only "strange" thing lwt does by default with signals
is to set a handler for SIGCHLD.

Actually here is a way to reproduce this behavior without lwt on OSX
and some other systems:

    # #load "unix.cma";;
    # Sys.set_signal Sys.sigchld (Sys.Signal_handle ignore);;
    - : unit = ()
    # Unix.system "true";;
    Exception: Unix.Unix_error (Unix.EINTR, "waitpid", "").

This will happen in any program setting a handler for SIGCHLD.

To avoid this you can:

- if you are using lwt, use Lwt_unix.system
- block SIGCHLD in the current thread while calling Unix.system
- write your own system function

Maybe this should be the default behavior.  Can you open a ticket on
mantis about this?

Cheers,
Jeremie

  parent reply	other threads:[~2013-03-15 11:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMu2m2Lt8oty_2mEQq8H1oV0-1Rjrf10ai543me9YxB1Nb5xfg@mail.gmail.com>
     [not found] ` <CALScVY=c1M=HAqMeM7x4QrxDTZsn0rB=HcTsQYheYUOBSBFRUQ@mail.gmail.com>
     [not found]   ` <CALScVYnt-m-dRR41rBPo5R3xDx-81tMwBFbM3q+5p4gRqsQC9w@mail.gmail.com>
     [not found]     ` <CALScVYmU7zEXbgdS21gGrq8iFvgVs0FWieKipRE9WtOM+PxeEg@mail.gmail.com>
2013-03-15  9:18       ` Florian Hars
2013-03-15 10:02         ` oliver
2013-03-15 10:11           ` David House
2013-03-15 11:38         ` Jeremie Dimino [this message]
2013-03-15 12:43           ` oliver
2013-03-15 13:17             ` Jeremie Dimino
2013-03-15 13:28               ` oliver
2013-03-15 13:43                 ` Jeremie Dimino
2013-03-15 13:24             ` Jeremie Dimino
2013-03-15 13:58               ` oliver
2013-03-15 14:05                 ` oliver
2013-03-15 14:16                   ` Jeremie Dimino
2013-03-15 14:18                     ` oliver
2013-03-15 14:17               ` oliver
2013-03-15 14:27                 ` oliver
2013-03-15 15:05                   ` Jeremie Dimino
2013-03-15 15:11                     ` oliver
2013-03-15 15:44                       ` Gabriel Kerneis
2013-03-15 16:00                         ` oliver
2013-03-15 16:12                           ` Gabriel Kerneis
2013-03-15 16:25                             ` oliver
2013-03-15 17:28                               ` Jeremie Dimino
2013-03-15 15:16                     ` oliver

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='CANhEzE5_OtOjxw5xAYd0S5pSwO906oXcXg=ZFu9+YnwGRLZ+Eg@mail.gmail.com' \
    --to=jdimino@janestreet.com \
    --cc=caml-list@inria.fr \
    --cc=ocsigen@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).