Thanks for the updated testcase! I was able to repro with that. > I am unable to trigger the crash in a `no-opt` build so getting a useful Pernosco session is likely out of the question, sorry. FWIW, pernosco is still useful with optimized-but-still-debuggable builds, e.g. `ac_add_options --enable-debug --enable-optimize="-O1"`. That's worth trying in these cases. (Some variables are still optimized out which can be a little annoying, but often you can infer their value from going up or down the stack or forward/backward in time.) I tried capturing an rr trace locally, and I was able to do so, with a debug-and-optimized build: https://pernos.co/debug/7Z0WKneMa1U4ney7Vnrl3w/index.html ...and also in an --enable-debug --disable-optimize build -- pernosco's still processing that trace, and I'll post the link when I get it.
Bug 1758199 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks for the updated testcase! I was able to repro with that. > I am unable to trigger the crash in a `no-opt` build so getting a useful Pernosco session is likely out of the question, sorry. FWIW, pernosco is still useful with optimized-but-still-debuggable builds, e.g. `ac_add_options --enable-debug --enable-optimize="-O1"`. That's worth trying in these cases. (Some variables are still optimized out which can be a little annoying, but often you can infer their value from going up or down the stack or forward/backward in time. And often ` --enable-optimize="-O1"` is enough to make us "win" race conditions in the same way that we do in fully-optimized builds.) I tried capturing an rr trace locally, and I was able to do so, with a debug-and-optimized build: https://pernos.co/debug/7Z0WKneMa1U4ney7Vnrl3w/index.html ...and also in an --enable-debug --disable-optimize build -- pernosco's still processing that trace, and I'll post the link when I get it.