JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... ) Used together with MCL_CURRENT , MCL_FUTURE , or both. Mark all current (with MCL_CURRENT ) or future (with MCL_FUTURE ) mappings to lock pages when they are faulted in. When used with MCL_CURRENT , all present pages are locked, but mlockall () will no ... t fault in non-present pages. When used with MCL_FUTURE , all future mappings will be marked to lock pages when they are faulted in, but they will not be populated by the lock when the mapping is crea ... スのアドレス空間にマップされたページと 一致しない。 ENOMEM Locking or unlocking a region would result in the total number of mappings with distinct attributes (e.g., locked versus unlocked) exceeding the allowed maximum. (For example, unlocking a range in ... ... ) Used together with MCL_CURRENT , MCL_FUTURE , or both. Mark all current (with MCL_CURRENT ) or future (with MCL_FUTURE ) mappings to lock pages when they are faulted in. When used with MCL_CURRENT , all present pages are locked, but mlockall () will no ... t fault in non-present pages. When used with MCL_FUTURE , all future mappings will be marked to lock pages when they are faulted in, but they will not be populated by the lock when the mapping is crea ... スのアドレス空間にマップされたページと 一致しない。 ENOMEM Locking or unlocking a region would result in the total number of mappings with distinct attributes (e.g., locked versus unlocked) exceeding the allowed maximum. (For example, unlocking a range in ... ... ) Used together with MCL_CURRENT , MCL_FUTURE , or both. Mark all current (with MCL_CURRENT ) or future (with MCL_FUTURE ) mappings to lock pages when they are faulted in. When used with MCL_CURRENT , all present pages are locked, but mlockall () will no ... t fault in non-present pages. When used with MCL_FUTURE , all future mappings will be marked to lock pages when they are faulted in, but they will not be populated by the lock when the mapping is crea ... スのアドレス空間にマップされたページと 一致しない。 ENOMEM Locking or unlocking a region would result in the total number of mappings with distinct attributes (e.g., locked versus unlocked) exceeding the allowed maximum. (For example, unlocking a range in ... ... ) Used together with MCL_CURRENT , MCL_FUTURE , or both. Mark all current (with MCL_CURRENT ) or future (with MCL_FUTURE ) mappings to lock pages when they are faulted in. When used with MCL_CURRENT , all present pages are locked, but mlockall () will no ... t fault in non-present pages. When used with MCL_FUTURE , all future mappings will be marked to lock pages when they are faulted in, but they will not be populated by the lock when the mapping is crea ... スのアドレス空間にマップされたページと 一致しない。 ENOMEM Locking or unlocking a region would result in the total number of mappings with distinct attributes (e.g., locked versus unlocked) exceeding the allowed maximum. (For example, unlocking a range in ... ... ) Used together with MCL_CURRENT , MCL_FUTURE , or both. Mark all current (with MCL_CURRENT ) or future (with MCL_FUTURE ) mappings to lock pages when they are faulted in. When used with MCL_CURRENT , all present pages are locked, but mlockall () will no ... t fault in non-present pages. When used with MCL_FUTURE , all future mappings will be marked to lock pages when they are faulted in, but they will not be populated by the lock when the mapping is crea ... スのアドレス空間にマップされたページと 一致しない。 ENOMEM Locking or unlocking a region would result in the total number of mappings with distinct attributes (e.g., locked versus unlocked) exceeding the allowed maximum. (For example, unlocking a range in ... ... ne of the following flags set: PROT_GROWSUP Apply the protection mode up to the end of a mapping that grows upwards. (Such mappings are created for the stack area on architectures---for example, HP-PARISC---that have an upwardly growing stack.) PROT_GROW ... ー EFAULT が間違って生成されていた)。 ENOMEM Changing the protection of a memory region would result in the total number of mappings with distinct attributes (e.g., read versus read/write protection) exceeding the allowed maximum. (For example, making the ... rotection of a range PROT_READ in the middle of a region currently protected as PROT_READ|PROT_WRITE would result in three mappings: two read/write mappings at each end and a read-only mapping in the middle.) バージョン pkey_mprotect () は Linux 4.9 で登 ... ... ne of the following flags set: PROT_GROWSUP Apply the protection mode up to the end of a mapping that grows upwards. (Such mappings are created for the stack area on architectures---for example, HP-PARISC---that have an upwardly growing stack.) PROT_GROW ... ー EFAULT が間違って生成されていた)。 ENOMEM Changing the protection of a memory region would result in the total number of mappings with distinct attributes (e.g., read versus read/write protection) exceeding the allowed maximum. (For example, making the ... rotection of a range PROT_READ in the middle of a region currently protected as PROT_READ|PROT_WRITE would result in three mappings: two read/write mappings at each end and a read-only mapping in the middle.) バージョン pkey_mprotect () は Linux 4.9 で登 ... ... ないものはダンプされない。 このファイルの各ビットは以下の意味を持つ。 bit 0 無名のプライベートマッピング (anonymous private mappings) をダンプする。 bit 1 無名の共有マッピング (anonymous shared mappings) をダンプする。 bit 2 ファイルと関連付けられたプライ ... ベートマッピング (file-backed private mappings) をダンプする。 bit 3 ファイルと関連付けられた共有マッピング (file-backed shared mappings) をダンプする。 bit 4 (Linux 2.6 ... ... 字を 指定する。これは特殊な意味に解釈される文字をエスケープするのに使用する。 デフォルトはバックスラッシュ (\) である。 The mapping section starts with the keyword CHARIDS in the first column. マッピング行は以下のフォーマットである。 <symbolic-name> <code ... ... を発揮するかは、オペレーティングシステムによります。 GNU/Linux の場合、 "use-coredump-filter" が無効となり、 "dump-excluded-mappings" が有効となります。 -o prefix 任意の引数 prefix を指定すると、コアダンプのファイル名を定める際のプレフィックスとして、その ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。