Finding Source of a UNIX Signal from Coredump Finding Source of a UNIX Signal from Coredump unix unix

Finding Source of a UNIX Signal from Coredump


unix crash gdb signals coredump

Recent-enough versions of the Linux kernel store this information in the core file. And, recent-enough versions of gdb can read it. Then you can use print $_siginfo with a core file just as you would when debugging live.

unix crash gdb signals coredump

You can also read this information from core dump by eu-readelf:

$ eu-readelf --notes coredump | headNote segment of 3180 bytes at offset 0x4a0:  Owner          Data size  Type  CORE                 336  PRSTATUS    info.si_signo: 6, info.si_code: 0, info.si_errno: 0, cursig: 6    sigpend: <>    sighold: <>    pid: 28046, ppid: 3774, pgrp: 28046, sid: 3774    utime: 0.000000, stime: 0.002895, cutime: 0.000000, cstime: 0.000000    orig_rax: 35, fpvalid: 1

Note info.si_signo: 6, which means that process was killed by SIGABRT.

Recent Posts
How can I color dots in a xy scatterplot according to column value?
How to update a claim in ASP.NET Identity?
What does {0} mean when initializing an object?
Accessing members of items in a JSONArray with Java
How to log SQL statements in Spring Boot?
Powershell Get-WebSite name parameter is ignored
How to detect scroll to bottom of html element
Java synchronized method
How to test controllers with CodeIgniter?
Detect Visual Composer
Matplotlib: Specify format of floats for tick labels
Rails join a list of strings with commas and "and" before the last