Results of 1 - 10 of about 12 for violation (0.003 sec.)
- Man page of ISATTY 13690
- ISATTY Section: Linux Programmer's Manual (3) Updated: 2019-03-06 Index JM Home Page 名前 isatty - ファイルディスクリプターが端末を参照しているかをチェックする 書式 #include < unistd.h > int isatty(int fd ); 説明 isatty () 関数は、 fd が端末
... le other than a terminal. On some older kernels, some types of files resulted in the error EINVAL in this case (which is a violation of POSIX, which specifies the error ENOTTY ). 属性 この節で使用されている用語の説明については、 attributes (7) を参照。 イ ...
-
https://man.mtool.work/man/20260915/man3/isatty.3.html
- Man page of SIGACTION 9533
- SIGACTION Section: Linux Programmer's Manual (2) Updated: 2020-12-21 Index JM Home Page 名前 sigaction, rt_sigaction - シグナルの動作の確認と変更 書式 #include < signal.h > int sigaction(int signum , const struct sigaction * act , struct si
... short si_addr_lsb; /* Least significant bit of address (since Linux 2.6.32) */ void *si_lower; /* Lower bound when address violation occurred (since Linux 3.19) */ void *si_upper; /* Upper bound when address violation occurred (since Linux 3.19) */ int si ...
-
https://man.mtool.work/man/20260915/man2/rt_sigaction.2.html
- Man page of SIGACTION 9533
- SIGACTION Section: Linux Programmer's Manual (2) Updated: 2020-12-21 Index JM Home Page 名前 sigaction, rt_sigaction - シグナルの動作の確認と変更 書式 #include < signal.h > int sigaction(int signum , const struct sigaction * act , struct si
... short si_addr_lsb; /* Least significant bit of address (since Linux 2.6.32) */ void *si_lower; /* Lower bound when address violation occurred (since Linux 3.19) */ void *si_upper; /* Upper bound when address violation occurred (since Linux 3.19) */ int si ...
-
https://man.mtool.work/man/20260915/man2/sigaction.2.html
- Man page of MREMAP 8490
- MREMAP Section: Linux Programmer's Manual (2) Updated: 2010-06-10 Index JM Home Page 名前 mremap - 仮想メモリーアドレスを再マッピングする 書式 #define _GNU_SOURCE /* feature_test_macros (7) 参照 */ #include < sys/mman.h > void *mremap(void
... メモリーが不正にアクセスされた場合 (例えば読み込み専用のセグメントに 書き込んだ場合)、セグメンテーション侵害 (segmentation violation) を 引き起こす。また、セグメント外の仮想メモリーにアクセスした場合にも セグメンテーション侵害が発生する。 mremap () は Lin ...
-
https://man.mtool.work/man/20260915/man2/mremap.2.html
- Man page of EXEC 8490
- EXEC Section: Linux Programmer's Manual (3) Updated: 2019-08-02 Index JM Home Page 名前 execl, execlp, execle, execv, execvp, execvpe - ファイルを実行する 書式 #include < unistd.h > extern char **environ; int execl(const char * pathname , c
... Before glibc 2.24, execl () and execle () employed realloc (3) internally and were consequently not async-signal-safe, in violation of the requirements of POSIX.1. This was fixed in glibc 2.24. アーキテクチャー固有の詳細 On sparc and sparc64, execv () is ...
-
https://man.mtool.work/man/20260915/man3/exec.3.html
- Man page of EXEC 8490
- EXEC Section: Linux Programmer's Manual (3) Updated: 2019-08-02 Index JM Home Page 名前 execl, execlp, execle, execv, execvp, execvpe - ファイルを実行する 書式 #include < unistd.h > extern char **environ; int execl(const char * pathname , c
... Before glibc 2.24, execl () and execle () employed realloc (3) internally and were consequently not async-signal-safe, in violation of the requirements of POSIX.1. This was fixed in glibc 2.24. アーキテクチャー固有の詳細 On sparc and sparc64, execv () is ...
-
https://man.mtool.work/man/20260915/man3/execl.3.html
- Man page of EXEC 8490
- EXEC Section: Linux Programmer's Manual (3) Updated: 2019-08-02 Index JM Home Page 名前 execl, execlp, execle, execv, execvp, execvpe - ファイルを実行する 書式 #include < unistd.h > extern char **environ; int execl(const char * pathname , c
... Before glibc 2.24, execl () and execle () employed realloc (3) internally and were consequently not async-signal-safe, in violation of the requirements of POSIX.1. This was fixed in glibc 2.24. アーキテクチャー固有の詳細 On sparc and sparc64, execv () is ...
-
https://man.mtool.work/man/20260915/man3/execle.3.html
- Man page of EXEC 8490
- EXEC Section: Linux Programmer's Manual (3) Updated: 2019-08-02 Index JM Home Page 名前 execl, execlp, execle, execv, execvp, execvpe - ファイルを実行する 書式 #include < unistd.h > extern char **environ; int execl(const char * pathname , c
... Before glibc 2.24, execl () and execle () employed realloc (3) internally and were consequently not async-signal-safe, in violation of the requirements of POSIX.1. This was fixed in glibc 2.24. アーキテクチャー固有の詳細 On sparc and sparc64, execv () is ...
-
https://man.mtool.work/man/20260915/man3/execlp.3.html
- Man page of EXEC 8490
- EXEC Section: Linux Programmer's Manual (3) Updated: 2019-08-02 Index JM Home Page 名前 execl, execlp, execle, execv, execvp, execvpe - ファイルを実行する 書式 #include < unistd.h > extern char **environ; int execl(const char * pathname , c
... Before glibc 2.24, execl () and execle () employed realloc (3) internally and were consequently not async-signal-safe, in violation of the requirements of POSIX.1. This was fixed in glibc 2.24. アーキテクチャー固有の詳細 On sparc and sparc64, execv () is ...
-
https://man.mtool.work/man/20260915/man3/execv.3.html
- Man page of EXEC 8490
- EXEC Section: Linux Programmer's Manual (3) Updated: 2019-08-02 Index JM Home Page 名前 execl, execlp, execle, execv, execvp, execvpe - ファイルを実行する 書式 #include < unistd.h > extern char **environ; int execl(const char * pathname , c
... Before glibc 2.24, execl () and execle () employed realloc (3) internally and were consequently not async-signal-safe, in violation of the requirements of POSIX.1. This was fixed in glibc 2.24. アーキテクチャー固有の詳細 On sparc and sparc64, execv () is ...
-
https://man.mtool.work/man/20260915/man3/execvp.3.html