| commit | 821da08a94a4e4cc9df57f3236d17e3d0dac02b7 | [log] [tgz] |
|---|---|---|
| author | Pau Espin Pedrol <pespin@sysmocom.de> | Wed Nov 25 18:00:58 2020 +0100 |
| committer | Pau Espin Pedrol <pespin@sysmocom.de> | Wed Nov 25 18:22:12 2020 +0100 |
| tree | 8c31e91ea3a542232a1b7235197ad5bccd30a6cf | |
| parent | dc9c785a2249081b2d419b8cb41e1e0a3fb68caf [diff] |
gbproxy: generate coredump and exit upon SIGABRT received Previous code relied on abort() switching sigaction to SIG_FDL + retriggering SIGABRT in case the signal handler returns, which would then generate the coredump + terminate the process. However, if a SIGABRT is received from somewhere else (kill -SIGABRT), then the process would print the talloc report and continue running, which is not desired. Change-Id: I97559b29328101c7cf340aaf1052c0c406634065 Fixes: OS#4865