You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder if winch could consider doing something similar; that is, register some signal handlers for fatal / deadly signals, and then use winch / libbacktrace to print a stack trace when that crash occurs?
This could be especially useful in debugging CI crashes.
The text was updated successfully, but these errors were encountered:
I put together a small experiment using
gdb
to print a backtrace when the process crashes. The core implementation lives here:https://github.com/kevinushey/mortem/blob/main/src/mortem.c
I wonder if
winch
could consider doing something similar; that is, register some signal handlers for fatal / deadly signals, and then usewinch
/libbacktrace
to print a stack trace when that crash occurs?This could be especially useful in debugging CI crashes.
The text was updated successfully, but these errors were encountered: