caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: oliver <oliver@first.in-berlin.de>
To: Matej Kosik <5764c029b688c1c0d24a2e97cd764f@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] signal-unsafety of %!
Date: Fri, 15 Mar 2013 17:02:32 +0100	[thread overview]
Message-ID: <20130315160232.GB5664@siouxsie> (raw)
In-Reply-To: <514344C4.4070908@gmail.com>

On Fri, Mar 15, 2013 at 03:56:52PM +0000, Matej Kosik wrote:
> On 15/03/13 14:36, oliver wrote:
> > On Fri, Mar 15, 2013 at 02:30:29PM +0000, Matej Kosik wrote:
> >> Hi,
> >>
> >> When I compile the attached program
> >>
> >>   (with compilers available directly from Debian's repositories)
> >>
> >> I can observe a (non-deterministic) deadlock.
> >>
> >> When I remove
> >>
> >> 	%!
> >>
> >> from the printf function inside the SIGALRM's handler, the deadlock never seem to occur.
> >>
> >> Obviously, interference can be easily introduced in concurrent programs; I was just surprised that even something like
> > [...]
> > 
> > 
> > Whats going on today?
> > 
> > Use Unix.sigprocmask.
> > 
> > Ciao,
> >    Oliver
> > 
> 
> Right, printf simply isn't reentrant.
> 
> (what I was observing was a program that was busy-looping, but stuck. I guess because internal shared data might have been damaged.).

Ah, yes, you used it inside the signal handler.
Have overlooked it.

Ciao,
   Oliver

      reply	other threads:[~2013-03-15 16:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15 14:30 Matej Kosik
2013-03-15 14:36 ` oliver
2013-03-15 15:56   ` Matej Kosik
2013-03-15 16:02     ` 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=20130315160232.GB5664@siouxsie \
    --to=oliver@first.in-berlin.de \
    --cc=5764c029b688c1c0d24a2e97cd764f@gmail.com \
    --cc=caml-list@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).