Closed mdavidsaver closed 4 years ago
On second thought, this should be a separate module. I'm going to want core dump analysis in basically all of my CI builds.
Why does that push for a separate module?
Complexity mainly. This code is hooking into OS specific hooks which aren't often used. And I think it benefits from its own (much faster) set of CI tests. work in progress at https://github.com/mdavidsaver/ci-core-dumper
Add core-dumper.py which hooks into the Linux kernel core_pattern facility to redirect core files. The net result is a stack trace of all threads for any test which produces a core (
SIGSEGV
orabort()
).The only added requirement is to have gdb installed. If it isn't, then core-dumper.py is a no-op (as on OSX). The rest is self-contained within
build.sh
.