coredump Analysis with gdb
Extract a crash report from a captured core dump without access to the developer machine.
A advanced Linux challenge worth 20 points. Solve it hands-on in a real Linux environment in your browser - no local setup, no fake shells.
The Challenge
A C++ service segfaults in production once per hour. A core dump was captured. The developer needs the faulting function and stack trace.
Your tasks:
- Find the core dump: ls /var/crash/ or ls /tmp/coredumps/
- Open with gdb: gdb /opt/app/service /path/to/core
- Inside gdb: run "bt full" to get the full backtrace
- Identify signal type, faulting function, top 5 stack frames
- Write to /tmp/crash_report.txt:
SIGNAL: <signal name> FAULT_FUNCTION: <function name> STACK: <5 lines of bt output>
- Run check to validate