Use of core dump

1. Use ulimit-a to view the information of the core file.
Core File size. If this row is 0, this function is disabled and core files are not generated.

2. Open Core dump.

On the Current compiled terminal, use the ulimit-C unlimited command to generate a core file with no size limit.

(Unlimited can also be the size of the generated core file, in kbyte .)

3. WhenProgramWhen Crash exits, the kernel willWorkDirectory to generate a core file (a memory image with debugging information added ).

4. Use GDB to view the core
$ GDB
Exe-file core. xxxx
Use BT or where to view the error.
Note: The executable file to be debugged must be added to-g during compilation so that the core file can display error information normally!

The following is the experience of using core dump on MySQL 3515:
1. The arm-hismall-Linux-GDB running on the PC cannot parse core dump, nor can it use PC-based GDB.
The cause of failure is that the core dump file is not matched with GDB.

Successful steps:
1. 3515sdk/pub/resource/gdb-6.8/directory is running GDB on the board, running GDB on the board.
2. File xxx
3. Core-file xxx