I have a script receiving a SIGABRT signal within a Jenkins job. It doesn't come from someone hitting "Abort" on the Jenkins interface.
The Jenkins job runs many compile, test, and infrastructure tasks. It has a Bazel frontend and a wrapper script that runs many (many) different test jobs. From somewhere, likely one of the test jobs, a SIGABRT signal is thrown. The SIGABRT signal is caught by Jenkins (or the bash script or the Bazel interface) and interrupts everything, not just the signaled application.
How can I deterministically find what specific executable this signal (or any signal, like SIGINT or SIGKILL) came from?
question from:https://stackoverflow.com/questions/65920481/how-can-i-determine-where-a-specific-sigabrt-comes-from
