JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... インスレッドはもう一つのスレッドに キャンセル要求を送信する。 $ ./a.out New thread started cnt = 0 cnt = 1 Canceling thread Called clean-up handler Thread was canceled; cnt = 0 上記の実行例から、スレッドがキャンセルされ、 キャンセルクリーンアップハンドラ ... が正常終了するようにし、さらに cleanup_pop_arg に 0 以外の値を渡している。 $ ./a.out x 1 New thread started cnt = 0 cnt = 1 Called clean-up handler Thread terminated normally; cnt = 0 上記では、スレッドはキャンセルされていないが、クリーンアップハンドラー ... static int done = 0; static int cleanup_pop_arg = 0; static int cnt = 0; static void cleanup_handler(void *arg) { printf("Called clean-up handler\n"); cnt = 0; } static void * thread_start(void *arg) { time_t start, curr; printf("New thread started\n" ... ... インスレッドはもう一つのスレッドに キャンセル要求を送信する。 $ ./a.out New thread started cnt = 0 cnt = 1 Canceling thread Called clean-up handler Thread was canceled; cnt = 0 上記の実行例から、スレッドがキャンセルされ、 キャンセルクリーンアップハンドラ ... が正常終了するようにし、さらに cleanup_pop_arg に 0 以外の値を渡している。 $ ./a.out x 1 New thread started cnt = 0 cnt = 1 Called clean-up handler Thread terminated normally; cnt = 0 上記では、スレッドはキャンセルされていないが、クリーンアップハンドラー ... static int done = 0; static int cleanup_pop_arg = 0; static int cnt = 0; static void cleanup_handler(void *arg) { printf("Called clean-up handler\n"); cnt = 0; } static void * thread_start(void *arg) { time_t start, curr; printf("New thread started\n" ... ... et) == SIGQUIT)) break; } According to POSIX.1, it is unspecified whether handlers registered using pthread_atfork (3) are called during the execution of system (). In the glibc implementation, such handlers are not called. glibc 2.1.3 より前のバージョ ... ... tems that do not support protection keys in hardware, pkey_mprotect () may still be used, but pkey must be set to -1. When called this way, the operation of pkey_mprotect () is equivalent to mprotect (). 例 以下のプログラムは、 mprotect () の使用方法を ... ync-signal-safe; see signal-safety (7). Nevertheless, we use printf() here as a simple way of showing that the handler was called. */ printf("Got SIGSEGV at address: %p\n", si->si_addr); exit(EXIT_FAILURE); } int main(int argc, char *argv[]) { int page ... ... tems that do not support protection keys in hardware, pkey_mprotect () may still be used, but pkey must be set to -1. When called this way, the operation of pkey_mprotect () is equivalent to mprotect (). 例 以下のプログラムは、 mprotect () の使用方法を ... ync-signal-safe; see signal-safety (7). Nevertheless, we use printf() here as a simple way of showing that the handler was called. */ printf("Got SIGSEGV at address: %p\n", si->si_addr); exit(EXIT_FAILURE); } int main(int argc, char *argv[]) { int page ... ... ng is done. However Linux waits for I/O completions, and thus sync () or syncfs () provide the same guarantees as fsync () called on every file in the system or filesystem respectively. In mainline kernel versions prior to 5.8, syncfs () will fail only ... ... ng is done. However Linux waits for I/O completions, and thus sync () or syncfs () provide the same guarantees as fsync () called on every file in the system or filesystem respectively. In mainline kernel versions prior to 5.8, syncfs () will fail only ... ... scriptor used to implement this stream. The file descriptor is still owned by stream and will be closed when fclose (3) is called. Duplicate the file descriptor with dup (2) before passing it to code that might close it. これらの処理を停止せずに行いたい ... ... scriptor used to implement this stream. The file descriptor is still owned by stream and will be closed when fclose (3) is called. Duplicate the file descriptor with dup (2) before passing it to code that might close it. これらの処理を停止せずに行いたい ... ... scriptor used to implement this stream. The file descriptor is still owned by stream and will be closed when fclose (3) is called. Duplicate the file descriptor with dup (2) before passing it to code that might close it. これらの処理を停止せずに行いたい ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。