This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Libc thread cancelation safety?

From: Florian Weimer <fw at deneb dot enyo dot de>
To: Dean Anderson <dean at av8 dot com>
Cc: gcc-help at gcc dot gnu dot org
Date: Fri, 20 Mar 2009 21:10:40 +0100
Subject: Re: Libc thread cancelation safety?
References: <Pine.LNX.4.44.0903201441410.1373-100000@citation2.av8.net>

* Dean Anderson:

> I have noticed that printf in glibc (glibc 2.3.5, i386) is not pthread
> cancellation safe, though printf on Solaris is cancellation safe.  
> Specifically, canceling a thread in printf leads to deadlock.
>
> What should one expect regarding cancelation safety in standard
> libraries?  Is this a bug in glibc?

Asynchronous cancellation is inherently unsafe.  I can't find a full
list of functions which may be called from a thread which is subject
to asynchronous cancellation right now, but it is undoubtly very short
and does not include anything which touches the heap or uses the stdio
I/O facilities.  Most bare system calls (read, write, close, pipe)
should be fine, though.

References:
- Libc thread cancelation safety?
  - From: Dean Anderson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]