fullcore — Enable/disable full core dump
fullcore —启用/禁用完整的核心转储
You can debug only one core dump at a time.
每次只能调试一个核心转储。
Run dbx on the binary executable that caused the core dump.
对导致核心转储的二进制可执行文件运行dbx。
The gdb shows what line of code caused the program to core dump.
gdb显示哪行代码导致程序发生核心转储。
You can delete the original core dump because it is within the ZIP.
您可以删除原始核心转储，因为它存在于这个 ZIP 文件中。
It is very important to diagnose the core dump to extract useful information.
重要的是诊断核心转储以便提取有用的信息。
This article gives instructions on how to collect data to debug the core dump problem.
本文提供有关如何收集数据来调试核心转储问题的说明。
A memory violation can spur SIGSEGV, killing the process instantly while leaving a core dump behind.
内存违例会引发SIGSEGV信号，立即终止进程，并留下一个内核转储。
If you try to use the same development machine for debugging this core dump, it might affect system performance.
如果尝试使用同一台开发计算机来调试此核心转储，则可能影响系统的性能。
When neither "panic" or "fatal" are found, sometimes a core dump will contain a reference to a "segmentation fault" in a function.
有时，当“panic”、“fatal”都没有找到时，核心转储将包含对函数中“segmentationfault”的引用。
When neither "panic" or "fatal" are found, sometimes a core dump will contain a reference to a "segmentation fault" in a function.
有时，当“panic”、“fatal”都没有找到时，核心转储将包含对函数中“segmentationfault”的引用。
应用推荐