How to analyze kernel dump

After the application [rtorrent] crashed, it produced a file core, 250 MB.

Caught Segmentation fault, dumping stack:B] [Port: 58940][U 0/0] [D 0/10] [H 1/32] [S 72/75/768] [F 0/128]
Stack dump not enabled.
Aborted (core dumped)

I need to analyze and see the stack trace in order to understand why rtorrent crashes so often.

+5
source share
1 answer

gdb should be able to analyze the kernel:

gdb /path/to/binary/rtorrent /path/to/coredump/rtorrent.core

enter whereto see the stack trace.

To see more: compile rtorrent with debugging symbols, start, wait for a crash and analyze the dump with gdb (in this case you can see the exact place where the crash occurs).

UPD : rtorrent libtorrent, , , .

+4

All Articles