I think it's because the wrong frame is interpreted by the wrong
thread but not entirely sure.
We do the naive thing, and just rebuild the stack trace / stack frame
stack. It shouldn't be all that expensive anyhow, seeing as how
most of it is probably cached by gdb.
I think it's because the wrong frame is interpreted by the wrong thread but not entirely sure.
We do the naive thing, and just rebuild the stack trace / stack frame stack. It shouldn't be all that expensive anyhow, seeing as how most of it is probably cached by gdb.