In article <537E2D2F.7000205%bbn.com@localhost>, Richard Hansen <rhansen%bbn.com@localhost> wrote: >Hi all, > >The Austin Group (POSIX standards body) is currently considering the >following bug report: > > Bug #615: pthread_setcancelstate should be async-signal-safe > http://austingroupbugs.net/view.php?id=615 > >Before acting on it, the group would like to know how existing >implementations behave. Is the NetBSD libpthread implementation of >pthread_setcancelstate() async-signal-safe? > >Specification of pthread_setcancelstate(): >http://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_setcancelstate.html > >Definition of async-signal-safe: >http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_27 > >Also see: >http://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_04_03_03 >http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xsh_chap02.html#tag_22_02_04_04 I think it is not because it calls pthread_exit() indirectly. christos