caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: oliver <oliver@first.in-berlin.de>
To: Jeremie Dimino <jdimino@janestreet.com>
Cc: caml-list@inria.fr, ocsigen@inria.fr
Subject: Re: [Caml-list] BUG in unix.ml (was: strange errors when linking lwt.unix)
Date: Fri, 15 Mar 2013 16:16:12 +0100	[thread overview]
Message-ID: <20130315151612.GB5194@siouxsie> (raw)
In-Reply-To: <CANhEzE48OVPjkbOsNoM9WCwY6z2evHvg1qJiufsCff_KZ5F72Q@mail.gmail.com>

On Fri, Mar 15, 2013 at 03:05:51PM +0000, Jeremie Dimino wrote:
[...]
> Actually OCaml is using sigaction(2).  It is only using signal(2) when
> sigaction is not available.
[...]

Possibly on non-unixoid systems, e.g. Windows.


> 
> Actually there are two different things here:
> 
> - signal disposition: this is a process-wide settings for each signal
> describing how to react when it is received.  It can be changed with
> the [sigaction] system call (or the less portable [signal]).
> - signal mask: it is a per-thread set of signals that are blocked.  It
> can be changed with sigprocmask.


sigprocmask and sigaction and so on all work on processes.

Mixing processes and threads (especially involving signals) can be tricky.


Using signal(2) is deprecated in general.

If you use Windows, it might be necessary,
because unix-moulde is for Unix.

Don't know if cygwin and similar environments allow
usage of unix-module. But even if they do, I'm not
sure it works like in real unixoid systems.


Ciao,
   Oliver

      parent reply	other threads:[~2013-03-15 15:16 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
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 [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=20130315151612.GB5194@siouxsie \
    --to=oliver@first.in-berlin.de \
    --cc=caml-list@inria.fr \
    --cc=jdimino@janestreet.com \
    --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).