1. Free space is not enough. 2. The ulimit for core is set to 0 in the account where the program is running. This disables core file creation.
3. The process sets a current working directory where it does not have write permissions. Since the core file is written into the current working directory, the core file cannot be written.Note: Use the chcore or syscorepath command to avoid this failure.
4. By default, all core files that are generated on an AIX system will have the name core. If a process is core dumping and the core file is being written, and another process terminates and attempts to write a core file in the same directory, the file core will be busy and the second process will not be able to write to the file.Note: Use the chcore or syscorepath command and unique core file naming to avoid this failure.
5. The process has set the SA_NODUMP flag in the call to sigaction(). You would need the source code for the program to verify that this is the reason for the core dump failure. Any program can prevent a core dump by setting this flag in a sigaction request.
6. If the suid or sgid bit is set on the executable, then it is possible that a core file will not be created. This can happen if the real user or group ID is not identical to the effective user or group ID.
7. A process attempts to write a core file into a directory where a core file already exists and the ownership and permissions on the file do not allow it to be overwritten.
8. A process attempts to write a core file into a directory where a core file already exists. This core file is owned by another user but has write permissions enabled on either group or other. The attempt to write the new core file results in the core file being zeroed out.
9. A process traps the signal whose default action is to create a core file but does not call the abort() function to actually create the core file.
10. A process ignores a signal that would, by default, generate a core file.
3. The process sets a current working directory where it does not have write permissions. Since the core file is written into the current working directory, the core file cannot be written.Note: Use the chcore or syscorepath command to avoid this failure.
4. By default, all core files that are generated on an AIX system will have the name core. If a process is core dumping and the core file is being written, and another process terminates and attempts to write a core file in the same directory, the file core will be busy and the second process will not be able to write to the file.Note: Use the chcore or syscorepath command and unique core file naming to avoid this failure.
5. The process has set the SA_NODUMP flag in the call to sigaction(). You would need the source code for the program to verify that this is the reason for the core dump failure. Any program can prevent a core dump by setting this flag in a sigaction request.
6. If the suid or sgid bit is set on the executable, then it is possible that a core file will not be created. This can happen if the real user or group ID is not identical to the effective user or group ID.
7. A process attempts to write a core file into a directory where a core file already exists and the ownership and permissions on the file do not allow it to be overwritten.
8. A process attempts to write a core file into a directory where a core file already exists. This core file is owned by another user but has write permissions enabled on either group or other. The attempt to write the new core file results in the core file being zeroed out.
9. A process traps the signal whose default action is to create a core file but does not call the abort() function to actually create the core file.
10. A process ignores a signal that would, by default, generate a core file.
3991
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
