Using libunwind for mac, since backtrace do not expect thread context…

[saf-e]

… (i.e. working just with current thread)

#skip-changelog

[codecov]

Codecov Report

Attention: Patch coverage is 55.00000% with 27 lines in your changes missing coverage. Please review.

Project coverage is 82.14%. Comparing base (d431ab9) to head (03eec55).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1088      +/-   ##
==========================================
- Coverage   82.38%   82.14%   -0.25%     
==========================================
  Files          53       53              
  Lines        7751     7811      +60     
  Branches     1216     1238      +22     
==========================================
+ Hits         6386     6416      +30     
- Misses       1253     1263      +10     
- Partials      112      132      +20     

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[supervacuus]

Thanks for the PR; introducing libunwind for macOS has been on our wish list for some time. This requires a bit more work on our side before we can merge it since ucontext-based stack tracing also affects the signal handler in the inproc backend. Further, the unwinder, as currently implemented, will have issues if system functions end up as leaves in the ucontext after being delivered from the signal trampoline.

If you are okay with it, I will take this over, adapt the current unwinder code for usage in inproc (and other signal handler users), and extract it into a separate unwinder module. But not before next week.

[saf-e]

If you are okay with it, I will take this over, adapt the current unwinder code for usage in inproc (and other signal handler users), and extract it into a separate unwinder module. But not before next week.

Yes, no problem with that, fill free to adapt it to your needs!