In both Pernosco traces, `DoLULBacktrace` wantes to copy > 261,700 bytes, it's restricted to `N_STACK_BYTES`=160KB, but then the `memcpy` triggers a SIGSEGV. Pernosco links near the `N_STACK_BYTES` check and just before the SIGSEGV: [debug](https://pernos.co/debug/gefrJF45YPulQnkvWBJabQ/index.html#f{m[AR3R,ApA_,t[0Q,Eu9U_,f{e[AR3R,AmQ_,s{afyf0yfAA,bAYs,uHoSlqg,oHpW/BQ___/), [no-debug](https://pernos.co/debug/4hZOME8ATDRlstWWcAqBhA/index.html#f{m[AuNj,Abk_,t[Ac4,E9Md_,f{e[AuNj,AaM_,s{afzR3FxAA,bAYk,uHQsiaQ,oHRzpTQ___/). We had had this problem in bug 1726125, where I was able to avoid these crashes by giving up if it wanted to copy >1MB. But it seems it's crashing now with a smaller copy. Markus, you know more about LUL (and rr?), would you mind having a look? Should we also give up when reaching `N_STACK_BYTES`? Is there a way to predict the SIGSEGV?
Bug 1753043 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
In both Pernosco traces, `DoLULBacktrace` wants to copy > 261,700 bytes, it's restricted to `N_STACK_BYTES`=160KB, but then the `memcpy` triggers a SIGSEGV. Pernosco links near the `N_STACK_BYTES` check and just before the SIGSEGV: [debug](https://pernos.co/debug/gefrJF45YPulQnkvWBJabQ/index.html#f{m[AR3R,ApA_,t[0Q,Eu9U_,f{e[AR3R,AmQ_,s{afyf0yfAA,bAYs,uHoSlqg,oHpW/BQ___/), [no-debug](https://pernos.co/debug/4hZOME8ATDRlstWWcAqBhA/index.html#f{m[AuNj,Abk_,t[Ac4,E9Md_,f{e[AuNj,AaM_,s{afzR3FxAA,bAYk,uHQsiaQ,oHRzpTQ___/). We had had this problem in bug 1726125, where I was able to avoid these crashes by giving up if it wanted to copy >1MB. But it seems it's crashing now with a smaller copy. Markus, you know more about LUL (and rr?), would you mind having a look? Should we also give up when reaching `N_STACK_BYTES`? Is there a way to predict the SIGSEGV?