JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... 得る必要があるような マルチスレッドプログラムでの使用に適している。 The random_r () function is like random (3), except that instead of using state information maintained in a global variable, it uses the state information in the argument pointed to by bu ... whose state is maintained in the object pointed to by buf , which must have been previously initialized by initstate_r (), instead of the seed associated with the global state variable. The initstate_r () function is like initstate (3) except that it in ... ... 得る必要があるような マルチスレッドプログラムでの使用に適している。 The random_r () function is like random (3), except that instead of using state information maintained in a global variable, it uses the state information in the argument pointed to by bu ... whose state is maintained in the object pointed to by buf , which must have been previously initialized by initstate_r (), instead of the seed associated with the global state variable. The initstate_r () function is like initstate (3) except that it in ... ... 得る必要があるような マルチスレッドプログラムでの使用に適している。 The random_r () function is like random (3), except that instead of using state information maintained in a global variable, it uses the state information in the argument pointed to by bu ... whose state is maintained in the object pointed to by buf , which must have been previously initialized by initstate_r (), instead of the seed associated with the global state variable. The initstate_r () function is like initstate (3) except that it in ... ... 得る必要があるような マルチスレッドプログラムでの使用に適している。 The random_r () function is like random (3), except that instead of using state information maintained in a global variable, it uses the state information in the argument pointed to by bu ... whose state is maintained in the object pointed to by buf , which must have been previously initialized by initstate_r (), instead of the seed associated with the global state variable. The initstate_r () function is like initstate (3) except that it in ... ... tion for the calling thread. The instruction is enabled by default. If disabled, any execution of a cpuid instruction will instead generate a SIGSEGV signal. This feature can be used to emulate cpuid results that differ from what the underlying hardware ... n, if a 32-bit TLS base address is used, arch_prctl () may use a real TLS entry as if set_thread_area (2) had been called, instead of manipulating the segment base register directly. Memory in the first 2 GB of address space can be allocated by using mm ... ... ら出たので、 glibc 2.1.3 では以下のようなリンク時の警告が追加された。 "the `llseek' function may be dangerous; use `lseek64' instead." これにより、警告なしでコンパイルしたい場合には、この関数を使用不可にできる。 Since glibc 2.28, this function symbol is n ... result , int whence ); 更に詳しい情報は、 llseek (2) を参照すること。 64-bit systems don't need an _llseek () system call. Instead, they have an lseek (2) system call that supports 64-bit file offsets. 属性 この節で使用されている用語の説明については、 a ... ... e */ /* followed by unsigned char cmsg_data[]; */ }; The sequence of cmsghdr structures should never be accessed directly. Instead, use only the following macros: * CMSG_FIRSTHDR () returns a pointer to the first cmsghdr in the ancillary data buffer ass ... accessing arbitrary payload data types. Applications should not cast it to a pointer type matching the payload, but should instead use memcpy (3) to copy data to or from a suitably declared object. * CMSG_LEN () は、 cmsghdr 構造体の cmsg_len メンバにデ ... ... e */ /* followed by unsigned char cmsg_data[]; */ }; The sequence of cmsghdr structures should never be accessed directly. Instead, use only the following macros: * CMSG_FIRSTHDR () returns a pointer to the first cmsghdr in the ancillary data buffer ass ... accessing arbitrary payload data types. Applications should not cast it to a pointer type matching the payload, but should instead use memcpy (3) to copy data to or from a suitably declared object. * CMSG_LEN () は、 cmsghdr 構造体の cmsg_len メンバにデ ... ... e */ /* followed by unsigned char cmsg_data[]; */ }; The sequence of cmsghdr structures should never be accessed directly. Instead, use only the following macros: * CMSG_FIRSTHDR () returns a pointer to the first cmsghdr in the ancillary data buffer ass ... accessing arbitrary payload data types. Applications should not cast it to a pointer type matching the payload, but should instead use memcpy (3) to copy data to or from a suitably declared object. * CMSG_LEN () は、 cmsghdr 構造体の cmsg_len メンバにデ ... ... e */ /* followed by unsigned char cmsg_data[]; */ }; The sequence of cmsghdr structures should never be accessed directly. Instead, use only the following macros: * CMSG_FIRSTHDR () returns a pointer to the first cmsghdr in the ancillary data buffer ass ... accessing arbitrary payload data types. Applications should not cast it to a pointer type matching the payload, but should instead use memcpy (3) to copy data to or from a suitably declared object. * CMSG_LEN () は、 cmsghdr 構造体の cmsg_len メンバにデ ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。