LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

signal-safety.7: Note glibc deviations from POSIX requirements 

See https://bugzilla.kernel.org/show_bug.cgi?id=25292

Reported-by: KASAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2016-11-09 13:42:37 +01:00
parent d1329af1f3
commit fb16ec3585
1 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
man7/signal-safety.7
View File

@ -301,6 +301,27 @@ or
.BR siglongjmp (3) .BR siglongjmp (3)
and the program subsequently calls an unsafe function, and the program subsequently calls an unsafe function,
then the behavior of the program is undefined. then the behavior of the program is undefined.
.\"
.SS Deviations in the GNU C library
The following known deviations from the standard occur in
the GNU C library:
.IP * 3
Before glibc 2.24,
.BR execl (3)
and
.BR execle (3)
employed
.BR realloc (3)
internally and were consequently not async-signal-safe.
.\" https://sourceware.org/bugzilla/show_bug.cgi?id=19534
This was fixed in glibc 2.24.
.IP *
.\" FIXME . https://sourceware.org/bugzilla/show_bug.cgi?id=13172
The glibc implementation of
.BR aio_suspend (3)
is not async-signal-safe because it uses
.BR pthread_mutex_lock (3)
internally.
.SH SEE ALSO .SH SEE ALSO
.BR sigaction (2), .BR sigaction (2),
.BR signal (7), .BR signal (7),