libera/#clasp - IRC Chatlog

1:51:56 Bike i did a quick survey of interpreted gf calls, since i have the compiler totally disabled, and man is the distribution skewed

1:52:51 Bike mean ~= 182,990, median = 0

1:53:34 Bike if you take only functions that have actually been called, it's 504,926 and 9490 respectively

1:56:44 Bike most called is #'cleavir-env::next, at twenty five million calls

2:03:25 Bike man, so if compiling it shaves a millisecond from each all, that's twenty five seconds... which sounds impressive until you remember how slow the compiler is

2:10:20 Bike although most of those calls to NEXT are in fact in the compiler, so... hm.

2:29:26 drmeister Bike: How can I figure out where the DynEnv's were defined?

2:36:28 Bike thaaaaat's pretty tricky. they have basically no source information or indicators

2:37:03 Bike you could look at the jmp_buf*, since that'll be in the frame, but that sucks

2:37:51 Bike this is why i mentioned compiler coordination earlier- as is there's very little, but if you want to keep doing this kind of debugging it'll make things a lot less painful

3:02:02 drmeister I see what's going on - we are unwinding over where we want to go.

3:02:04 drmeister https://usercontent.irccloud-cdn.com/file/iya0W3gw/image.png

3:02:17 drmeister On the left is at the start of a sjlj_unwind.

3:03:22 drmeister The dest is the second TagbodyEnv_O @ 0x7f3c709fa849

3:03:45 drmeister Bit it skips over to 0x7f3c709fa939

3:04:01 drmeister Then the dest is not on the DynEnv stack.

3:04:10 drmeister I can get the source locations.

3:04:58 drmeister I printed the DynEnv stack on the left at the start of the sjlj_unwind and the DynEnv stack after the first proceed.

3:05:04 drmeister on the right

3:09:36 Bike huh. i wonder why the heck that would be happening.

3:09:51 Bike also, i wonder if we should find some way to coalesce bindings, but that's not important

3:15:30 drmeister The sjlj_unwind is being called with this on the backtrace...

3:15:32 drmeister https://www.irccloud.com/pastebin/16hgNOya/

3:15:49 drmeister CORE::DELETE-LIST

3:17:07 Bike i... did not know that could unwind... i guess from a test or key?

3:17:31 Bike well, and if it's bytecompiled it'll do some unwinding

3:18:10 Bike oh, heck, it's from the m-v-bind

3:18:19 Bike that shouldn't even be nonlocal. dangit.

3:20:31 drmeister This is the backtrace for the TagbodyEnv destination - the same function (of course)

3:20:33 drmeister https://www.irccloud.com/pastebin/Epn828Mc/

3:22:23 drmeister This is on the stack when the UnwindProtect that it unwinds to is put on the stack

3:22:24 drmeister https://www.irccloud.com/pastebin/7oqmSdxo/

3:23:31 Bike ack, this involves threads somehow

3:26:15 drmeister It's very reproducible.

3:26:39 drmeister How do you see threads?

3:28:38 Bike there's a Process_O in that last backtrace

3:34:11 drmeister It's unwinding out of the TPL frame.