Searched refs:handlers (Results 1 – 25 of 30) sorted by relevance
12
| /glibc-2.36/htl/ |
| D | pt-exit.c | 36 struct __pthread_cancelation_handler **handlers; in __pthread_exit() local
44 for (handlers = __pthread_get_cleanup_stack (); in __pthread_exit()
45 *handlers != NULL; in __pthread_exit()
46 *handlers = (*handlers)->__next) in __pthread_exit()
47 (*handlers)->__handler ((*handlers)->__arg); in __pthread_exit()
|
| /glibc-2.36/manual/ |
| D | macros.texi | 66 @c Document a function as safe for use in asynchronous signal handlers.
72 @c handlers. This distinguishes unmarked functions, for which this
|
| D | process.texi | 108 protected using cancellation handlers.
254 @c handlers, and unlocks the internal lock. The child bumps the fork
257 @c loader lock, runs the child handlers, reseting ref counters to 1, and
259 @c handlers themselves are unsafe.
608 protected using cancellation handlers.
695 protected using cancellation handlers.
|
| D | intro.texi | 225 asynchronous signal handlers. AS, in AS-Safe, stands for Asynchronous
230 unsuitable for use in signal handlers. However, programs could
231 misbehave should asynchronous signal handlers modify this thread-local
233 preserve it. Therefore, signal handlers that call functions that may
252 Just like signal handlers, cancellation cleanup routines must configure
355 failure to notice updates made by signal handlers.
446 AS-Unsafe, because calling them in signal handlers may interfere with
496 before configuring signal handlers or enabling cancellation, so that the
669 handlers or blocking signals that might use it, and holding a lock while
837 threads or within asynchronous signal or cancellation handlers.
|
| D | signal.texi | 33 * Interrupted Primitives:: Signal handlers affect use of @code{open},
262 program incurs an error. These programs have handlers which use
266 terminate. If you block or ignore these signals or establish handlers
940 This is the type of signal handler functions. Signal handlers take one
1357 File}), any signals that you've defined your own handlers for revert to
1362 handlers.
1368 own signal handlers.
1869 allocate in advance space for signal handlers to use.
1881 signal handlers because they block signals. As a result, the library
1883 handlers. The obstack allocation functions are safe as long as you
[all …]
|
| D | llio.texi | 162 protected using cancellation handlers.
247 protected using cancellation handlers.
453 protected using cancellation handlers.
651 protected using cancellation handlers.
814 protected using cancellation handlers.
2257 protected using cancellation handlers.
3351 be protected using cancellation handlers.
|
| D | memory.texi | 367 @c be safe to call from within signal handlers. Error-checking mutexes
1273 @c within signal handlers or left behind in case of cancellation.
1591 handlers for the functions @code{malloc}, @code{realloc}, and
1612 Otherwise it deinstalls the handlers for @code{malloc}, @code{realloc},
|
| D | terminal.texi | 1726 protected using cancellation handlers.
1872 handlers for job control signals that reset terminal modes. The above
|
| D | startup.texi | 997 @c calls from signal handlers, but if we're in the middle of flushing or
|
| D | conf.texi | 930 should be enough for basic scenarios involving simple signal handlers
|
| D | errno.texi | 48 possibility except when writing signal handlers.
|
| D | resource.texi | 550 Interrupt handlers live in that limbo between processes. The CPU is
|
| D | arith.texi | 755 @c handlers.
1042 @strong{NB:} @w{IEEE 754} says that trap handlers are given details of
|
| D | math.texi | 1681 @c partially-updated state in case of calls from within signal handlers
|
| D | stdio.texi | 2979 * Predefined Printf Handlers:: Predefined @code{printf} handlers.
3128 be used freely by the user-defined handlers but when called from
|
| D | charset.texi | 813 @c signal handlers may encounter gconv databases or caches in a
|
| D | time.texi | 3052 be protected using cancellation handlers.
|
| D | texinfo.tex | 2870 % The following should really be moved into \setupmarkupstyle handlers.
|
| /glibc-2.36/ChangeLog.old/ |
| D | ChangeLog.ports-powerpc | 52 handlers.
|
| D | ChangeLog.17 | 4352 Try installed handlers even for existing format specifiers first.
4725 * stdlib/cxa_finalize.c: Remove quick_exit handlers, don't call them.
14608 more exit handlers, call them right away.
|
| D | ChangeLog.7 | 1778 Tell about cleanup handlers & fcntl,lseek,write,read,close,open.
1779 * manual/process.texi: Tell about cleanup handlers & system,waitpid,
11434 before using registered handlers and don't test
|
| D | ChangeLog.nptl | 9224 * tst-cancel4.c: Also check cancellation handlers.
11551 (__unregister_atfork): Free the memory allocated for the handlers
|
| D | ChangeLog.22 | 3985 hurd: implement SA_SIGINFO signal handlers.
|
| D | ChangeLog.5 | 9231 elts with null handlers.
|
| /glibc-2.36/ |
| D | NEWS | 102 [27054] libc: pthread_atfork handlers that call pthread_atfork
1887 * The popen and system do not run atfork handlers anymore (BZ#17490).
1889 pthread_atfork documentation regarding atfork handlers is to handle
1983 [17490] stdio: popen should not invoke atfork handlers
3966 [14499] nptl: Does posix_spawn invoke atfork handlers / use vfork?
3967 [14750] libc: Race condition in posix_spawn vfork usage vs signal handlers
|
12