Hello
Thanks for a super useful package!
I wonder if you can give us any clues as to how we go about debugging the below stacktrace.
This is the only output we are getting from the segfault handler:
root@ifu-20:/data/crashlogs# cat segfault_1677286402019.log
=========== Caught a Segmentation Fault [pid=417] ===========
-----[ Native Stacktraces ]-----
[pc=0x00000000b43269a0, sp=0x00000000bec5bb68] in segfault_handler(int)+0x48
[pc=0x00000000b6680061, sp=0x00000000bec5bb78] in sigset+0xd8
[pc=0x000000003ca490c8, sp=0x00000000bec5be74] in +0xd8
---[ V8 JavaScript Stacktraces ]---
============================================================
Have you got any ideas about where we go from here to debug it? We only see it sporadically, sometimes it will happen a few times in a row and then not happen again for weeks. We are going to start disabling node modules that have native code and see if we can narrow it down that way.
Hello
Thanks for a super useful package!
I wonder if you can give us any clues as to how we go about debugging the below stacktrace.
This is the only output we are getting from the segfault handler:
Have you got any ideas about where we go from here to debug it? We only see it sporadically, sometimes it will happen a few times in a row and then not happen again for weeks. We are going to start disabling node modules that have native code and see if we can narrow it down that way.