AIX系统中不产生CORE文件的十大理由

http://blog.sina.com.cn/s/blog_53401bdf0100fl40.html

没有足够的空间，文件系统写的核心文件。	REASON CODE 原因代码  ENOSPC   28 ENOSPC 28
2) The ulimit for core is set to 0 in the account where the program is running. 2）为核心的ulimit设置账户中为0该程序正在运行。 This disables core file creation.这将禁用的核心文件的创建。	REASON CODE 原因代码 EPERM     1 EPERM 1 CORE FILE NAME 核心文件名称 blank 空白
3) The process sets a current working directory where it does not have write permissions. 3）设置一个进程的当前工作目录的地方没有写权限。 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. 注意：使用chcore或syscorepath命令 ， 以避免这种失败。	REASON CODE 原因代码 EACCES   13 EACCES 13  CORE FILE NAME 核心文件名称  path 路径  path to where the system attempted to write the core file. 路径在系统试图写入核心文件。
4) By default, all core files that are generated on an AIX system will have the name core. 4）默认情况下，所有核心是在AIX系统产生将有名字的核心文件。 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. 注意：使用chcore或syscorepath指挥和独特的核心文件命名 ， 以避免这种失败。	REASON CODE 原因代码 EAGAIN   11 EAGAIN 11 OR 或 EACCES   13 EACCES 13
5) The process has set the SA_NODUMP flag in the call to sigaction(). 5）进程已在向sigaction调用SA_NODUMP标志（）。 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.可以防止任何程序通过设置在sigaction请求此标志一个核心转储。	REASON CODE 原因代码 EPERM     1 EPERM 1
6) If the suid or sgid bit is set on the executable, then it is possible that a core file will not be created. 6）如的SUID或SGID位的可执行文件，那么很可能是一个核心文件将不会被创造的。 This can happen if the real user or group ID is not identical to the effective user or group ID.发生这种情况，如果真正的用户或组ID是不一样的有效用户或组ID。 See theexample at the end of this document that illustrates this scenario.见在本文件，说明了这种情况下结束的例子 。	REASON CODE 原因代码 EPERM     1 EPERM 1 CORE FILE NAME 核心文件名称 blank 空白
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. 7）进程试图写入到一个目录中的核心文件，其中一个核心文件已经存在，所有权和文件上的权限不允许它被覆盖。 See the example at the end of this document that illustrates this scenario.见在本文件，说明了这种情况下结束的例子 。 Note: Use the chcore or syscorepath command to avoid this failure. 注意：使用chcore或syscorepath命令 ， 以避免这种失败。	REASON CODE 原因代码 EACCES  13 EACCES 13  CORE FILE NAME 核心文件名称  path 路径  path to where the system attempted to write the core file. 路径在系统试图写入核心文件。
8) A process attempts to write a core file into a directory where a core file already exists. 8）进程试图写入到一个目录中的核心文件，其中一个核心文件已存在。 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.企图写入新的核心，核心文件的结果文件被归零。 See the example at the end of this document that illustrates this scenario.见在本文件，说明了这种情况下结束的例子 。 Note: Use the chcore or syscorepath command to avoid this failure. 注意：使用chcore或syscorepath命令 ， 以避免这种失败。	REASON CODE 原因代码 EPERM     1 EPERM 1  CORE FILE NAME 核心文件名称  path 路径  path to where the system attempted to write the core file. 路径在系统试图写入核心文件。 Note: Some versions of AIX do not add the CORE_DUMP_FAILED entry to the error report. 注：某些版本的AIX不添加CORE_DUMP_FAILED进入错误报告。
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. 9）一个进程陷阱的信号，其默认操作是创建一个核心文件，但不调用abort（）函数实际创建核心文件。	No CORE_DUMP_FAILED entry没有CORE_DUMP_FAILED进入
10) A process ignores a signal that would, by default, generate a core file. 10）一个进程忽略的信号，将默认情况下，生成一个核心文件。 See the example at the end of this document that provides a procedure for determining if this is the cause of a failed core dump.见在本文件规定了确定程序结束的例子 ，如果这是一个失败的核心转储的原因。	No CORE_DUMP_FAILED entry没有CORE_DUMP_FAILED进入