This is the mail archive of the libc-help@sourceware.org mailing list for the glibc 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: Determining cancellation points in glibc

From: Mike Frysinger <vapier at gentoo dot org>
To: libc-help at sourceware dot org
Cc: Loic Domaigne <tech at domaigne dot com>,"Carlos O'Donell" <carlos at systemhalted dot org>,mtk dot manpages at gmail dot com
Date: Thu, 27 Nov 2008 14:17:04 -0500
Subject: Re: Determining cancellation points in glibc
Organization: wh0rd.org
References: <cfd18e0f0811240927u1424bbadxc4907ef15210794a@mail.gmail.com> <119aab440811250552g5a162a27r5772fba9b5eb63b@mail.gmail.com> <492C6448.8090302@domaigne.com>

On Tuesday 25 November 2008 15:47:04 Loic Domaigne wrote:
> The next issue I see: POSIX states that the no other functions except
> the ones listed in the mandatory and optional list may be CP. So a
> natural question arise: how does the Glibc folks enforce this? Through
> code review? Other means, like compiler flags etc. ?

code review only atm for optional.  due to the nesting Carlos highlights, it's 
pretty hard to statically trace everything.

most mandatory points are checked with `nm` ... look at the nptl tests.
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.

References:
- Determining cancellation points in glibc
  - From: Michael Kerrisk
- Re: Determining cancellation points in glibc
  - From: Carlos O'Donell
- Re: Determining cancellation points in glibc
  - From: Loic Domaigne

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