JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... orms the necessary preparatory steps for execution of the signal handler: a) The signal is removed from the set of pending signals. b) If the signal handler was installed by a call to sigaction (2) that specified the SA_ONSTACK flag and the thread has d ... efined an alternate signal stack (using sigaltstack (2)), then that stack is installed. c) Various pieces of signal-related context are saved into a s ... register state required for resuming the interrupted program; + the thread's current signal mask; + the thread's alternate signal stack settings. (If the signal handler was installed using the sigaction (2) SA_SIGINFO flag, then the above information is ... ... ocket (see unix (7)). In the receiving process, a read (2) from the received file descriptor will return information about signals queued to that process. execve (2) での扱い 他のファイルディスクリプターと全く同様に、 signalfd ファイルディスクリプターも ... adds (via epoll_ctl (2)) a signalfd file descriptor to an epoll (7) instance, then epoll_wait (2) returns events only for signals sent to that process. In particular, if the process then uses fork (2) to create a child process, then the child will be a ... ble to read (2) signals that are sent to it using the signalfd file descriptor, but epoll_wait (2) will not indicate that the signalfd file descri ... ... ocket (see unix (7)). In the receiving process, a read (2) from the received file descriptor will return information about signals queued to that process. execve (2) での扱い 他のファイルディスクリプターと全く同様に、 signalfd ファイルディスクリプターも ... adds (via epoll_ctl (2)) a signalfd file descriptor to an epoll (7) instance, then epoll_wait (2) returns events only for signals sent to that process. In particular, if the process then uses fork (2) to create a child process, then the child will be a ... ble to read (2) signals that are sent to it using the signalfd file descriptor, but epoll_wait (2) will not indicate that the signalfd file descri ... ... とになる。 どのスレッドがシグナルを受信するかは決まっていない。 sigwaitinfo () or sigtimedwait (), can't be used to receive signals that are synchronously generated, such as the SIGSEGV signal that results from accessing an invalid memory address or the ... SIGFPE signal that results from an arithmetic error. Such signals can be caught only via signal handler. POSIX では sigtimedwait () の引数 timeout の値を NULL にした場合の意味を未定義として ... The glibc wrapper functions for sigwaitinfo () and sigtimedwait () silently ignore attempts to wait for the two real-time signals that are used internally by the NPTL threading implementation. See nptl (7) for details. The original Linux system call wa ... ... とになる。 どのスレッドがシグナルを受信するかは決まっていない。 sigwaitinfo () or sigtimedwait (), can't be used to receive signals that are synchronously generated, such as the SIGSEGV signal that results from accessing an invalid memory address or the ... SIGFPE signal that results from an arithmetic error. Such signals can be caught only via signal handler. POSIX では sigtimedwait () の引数 timeout の値を NULL にした場合の意味を未定義として ... The glibc wrapper functions for sigwaitinfo () and sigtimedwait () silently ignore attempts to wait for the two real-time signals that are used internally by the NPTL threading implementation. See nptl (7) for details. The original Linux system call wa ... ... とになる。 どのスレッドがシグナルを受信するかは決まっていない。 sigwaitinfo () or sigtimedwait (), can't be used to receive signals that are synchronously generated, such as the SIGSEGV signal that results from accessing an invalid memory address or the ... SIGFPE signal that results from an arithmetic error. Such signals can be caught only via signal handler. POSIX では sigtimedwait () の引数 timeout の値を NULL にした場合の意味を未定義として ... The glibc wrapper functions for sigwaitinfo () and sigtimedwait () silently ignore attempts to wait for the two real-time signals that are used internally by the NPTL threading implementation. See nptl (7) for details. The original Linux system call wa ... ... て返される (但し、 oldset が NULL でない場合)。 A set of functions for modifying and inspecting variables of type sigset_t ("signal sets") is described in sigsetops (3). マルチスレッドのプロセスで sigprocmask () を使用した場合の動作は規定されていない。 pt ... in the kernel sources). The glibc wrapper function for sigprocmask () silently ignores attempts to block the two real-time signals that are used internally by the NPTL threading implementation. See nptl (7) for details. The original Linux system call wa ... s named sigprocmask (). However, with the addition of real-time signals in Linux 2.2, the fixed-size, 32-bit sigset_t (referred to as old_kernel_sigset_t in this manual page) type supported by t ... ... て返される (但し、 oldset が NULL でない場合)。 A set of functions for modifying and inspecting variables of type sigset_t ("signal sets") is described in sigsetops (3). マルチスレッドのプロセスで sigprocmask () を使用した場合の動作は規定されていない。 pt ... in the kernel sources). The glibc wrapper function for sigprocmask () silently ignores attempts to block the two real-time signals that are used internally by the NPTL threading implementation. See nptl (7) for details. The original Linux system call wa ... s named sigprocmask (). However, with the addition of real-time signals in Linux 2.2, the fixed-size, 32-bit sigset_t (referred to as old_kernel_sigset_t in this manual page) type supported by t ... ... 可能でない場合、 多くのプログラムの動作がおかしくなるだろう。 Since Linux 2.6.31, reads from /dev/zero are interruptible by signals. (This change was made to help with bad latencies for large reads from /dev/zero .) 関連項目 chown (1), mknod (1), full (4 ... ... 可能でない場合、 多くのプログラムの動作がおかしくなるだろう。 Since Linux 2.6.31, reads from /dev/zero are interruptible by signals. (This change was made to help with bad latencies for large reads from /dev/zero .) 関連項目 chown (1), mknod (1), full (4 ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。