Bug #2321
closedosmo-gsm-tester: store properly coredump files when a process crashes
100%
Description
When a process crashes (both on main unit or on the BTS), we should be able to record the details and store the coredump in the run directory of the trial.
- Configure the main unit correctly (ulimit, etc.) to output the core dump in the run directory of the crashed process, together with its stderr and stdout files.
- Same for the BTs + scp it back to the trial directory in the main unit.
- Extra: Add python code to automatically open the dump file and print a backtrace + other interesting stuff.
This can be tested apparently by sending a SIGQUIT signal to a process: https://stackoverflow.com/questions/6561194/force-a-core-to-dump-from-an-active-normally-running-program-on-freebsd
Updated by pespin almost 7 years ago
- Subject changed from osmo-gsm-tester: store properly coredump files whena process crash to osmo-gsm-tester: store properly coredump files when a process crashes
Updated by neels almost 7 years ago
- Related to Bug #2325: sporadic shutdown of osmo-bts-trx in osmo-gsm-tester runs (no clock from trx) added
Updated by neels almost 7 years ago
I remember to have seen a core file in a result tarball before, so I assumed this would work;
(except for the sysmobts, where we simply don't have code to copy a core file back to the workspace yet.)
Updated by neels almost 7 years ago
The recent "crash" of osmo-bts-trx that made us question the working core dumps is actually an intentional shutdown by osmo-bts-trx (see #2325) and is not expected to produce a core dump. Anyway, it can't hurt to verify that core dumps are working as intended.
Updated by neels almost 7 years ago
- Related to deleted (Bug #2325: sporadic shutdown of osmo-bts-trx in osmo-gsm-tester runs (no clock from trx))
Updated by pespin over 6 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
I verified that crash dumps are working correctly. I added some bits to osmo-gsm-tester manuals which were missing.
I had a brief look at automatically dumping the backtrace with gdb but doesn't seem to have high priority as anyway we have all binaries available in the tar.gz and can be easily debugged at any time.
