rupprecht added a comment.

Thanks, I'll take a look at that.

For SIGTERM (issued by test runners to handle timeouts), the stack trace is 
printed via `faulthandler.register(signal.SIGTERM, chain=True)`. The 
`chain=True` //should// cause previous signal handlers registered for SIGTERM 
to execute.

For all other signal types, this is enabled with `faulthandler.enable()`, and 
there doesn't appear to be any equivalent option AFAICT, so it's plausible that 
it's overwriting the signal handler. Maybe we could replace that with calls to 
`faulthandler.register()` for each signal, but hopefully there's a cleaner way.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D87637/new/

https://reviews.llvm.org/D87637

_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to