23:46:14aethnot actually checking type unless the right implementation/optimization combination is present is so weird
23:46:33aethanother thing that's common is not exporting class/type names so you have to check-type on foo::bar
23:47:10aethif you let me make a bar, let me check-type on the bar without having to use ::
1:40:04mathrickBike: huh! New development. I was looking at the SBCL manual to see if it would help me make sense of of the LDB backtrace, and it mentioned looking at all threads, which I did, and there was a surprising number of them. So I went and disabled loading Verbose, which spawns background threads, and sure enough, the crash is gone
1:40:31mathrickI still have no idea why it somehow persists between runs, but at least that's a clue
1:41:38mathrickthe test code that's crashing isn't even using Verbose for anything, so merely loading it is enough to mess with things
1:58:29Bikeoh boy, maybe it's some horrid concurrency problem