Though I haven't cleaned it up yet, backtrace printing works when manually calling print() (though libunwind doesn't seem to give file names or line numbers). Unfortunately, naively translating the signal handling code to macOS didn't seem to work (the backtrace printing logic doesn't seem to be called). I might revisit this in the future, but I wouldn't mind if someone who understands signal handling better than me was interested in picking up the baton.
Though I haven't cleaned it up yet, backtrace printing works when manually calling
print()
(thoughlibunwind
doesn't seem to give file names or line numbers). Unfortunately, naively translating the signal handling code to macOS didn't seem to work (the backtrace printing logic doesn't seem to be called). I might revisit this in the future, but I wouldn't mind if someone who understands signal handling better than me was interested in picking up the baton.13