Debugging a core dump
If a program crashes with a core dump then, it is easy to debug and find the last internal state of the program. When we run multiple programs or threads, then it is difficult to find which core was generated by which process. To resolve this, there are a few settings available in /proc, which will help us to add more detail in the core file name.
Support available from Kernel v2.4. Setting '1' to this file, will generate a core file with PID. For example: core.1234
Support available from Kernel v2.5. This file provides more control to form the core file name.
This is very similar to setting the core_uses_pid option.
echo "core.%p" > /proc/sys/kernel/core_pattern
By setting this value, core file will be generated with the following details: executable filename, PID of the dumped process and number of the signal causing the dump.
echo "core.%e.%p.%s" > /proc/sys/kernel/core_pattern
More useful options are explained in the proc man page.
This Tech Tip was brought to us by Bharathi in Chennai, India. Thanks, Bharathi!
Instant fame is easy at Linux Journal. Just send us your useful Tech Tips to share with the Linux Community, and we'll send you a cool t-shirt for your efforts!
Please note: Tech Tips featured in this specific section of LinuxJournal.com are kindly brought to us by readers and are not necessarily tested by LinuxJournal.com editors.
- Readers' Choice Awards 2013
- Linux Kernel News - November 2013
- RSS Feeds
- Sublime Text: One Editor to Rule Them All?
- Mars Needs Women
- December 2013 Issue of Linux Journal: Readers' Choice
- Raspberry Pi: the Perfect Home Server
- Linux Systems Administrator
- Advanced Hard Drive Caching Techniques
- Technical Support Rep
- Reply to comment | Linux Journal
3 hours 22 min ago
- "Redis RethinkDB 4.5%" on Best NoSQL Databases
13 hours 28 min ago
- on the ground
19 hours 49 min ago
- I was able to read the whole
21 hours 18 min ago
- since i have read the title i
1 day 39 min ago
- Belanja Online Cari Voucher Diskon
1 day 44 min ago
- The kernel doesn't really
1 day 12 hours ago
1 day 13 hours ago
1 day 13 hours ago
1 day 15 hours ago