no dead-lock when signal handler calls localtime_r() on FreeBSD, but on Linux

Matthias Apitz guru at
Mon Oct 2 07:10:04 UTC 2017

El día Monday, October 02, 2017 a las 09:57:51AM +0300, Yuri Pankov escribió:

> On Mon, 2 Oct 2017 08:34:26 +0200, Matthias Apitz wrote:
> >
> >
> >Hello,
> >
> >I'm on the way clarifying a deadlock-issue we face on Linux when localtime_r()
> >is called in a signal-handler funtion. If you compile the code attached
> >below with gcc on Linux, the code gives what one deserves: a dead-lock
> >when Ctrl-C is pressed.
> Why? I don't see anything explicitly stating that localtime_r() is
> async-signal-UNsafe.

Because, as I said, it is not in the list of 

     The following functions are either reentrant or not interruptible by
     signals and are async-signal safe.  Therefore applications may invoke
     them, without restriction, from signal-catching functions or from a child
     process after calling fork(2) in a multi-threaded process:

in the man page sigactio(2).

Matthias Apitz               |  /"\   ASCII Ribbon Campaign:
E-mail: guru at     |  \ /   - No HTML/RTF in E-mail
WWW: |   X    - No proprietary attachments
phone: +49-176-38902045      |  / \   - Respect for open standards

More information about the freebsd-questions mailing list