21:09:39Bikeit sounds like the problem is unwinding past where we should be, so i guess it would make sense to trace entry into sjlj_unwind_proceed and figure out whether the destination is actually live when we start each sub-exit
21:54:50Bikethere's also of course the question of why this is only happening now
22:02:29drmeisterIt’s definitely unwinding last where it should be.
22:03:06drmeisterIt’s calling sjlj_continue_unwinding after a cleanup clause.
22:03:37drmeisterAnd I think it’s unwinding in the cleanup clause of the TPL function.
22:03:58Bikeuhhuh... do you know where the unwind initially results from?
22:04:14Bikelike, what is return-from-ing or go-ing or whatever.
22:06:47drmeisterYes and yes - but I’m afk at the moment. I posted details above. When I get back to my computer if you are up for it we could try figuring this out together.
22:08:01drmeisterI’ve added debugging tools that will help sort it out. We can now dump the dynenv stack and it shows where in the regular stack unwinding goes to.
22:11:26Bikehm, maybe it's just unwinding through tpl because tpl is used for the debug repl, though
22:14:43drmeisterYeah - but it interferes with debugging.