Thank you for the fast response!
Re QEMU, I was afraid so. :-(
The number 100940122304 (actually a bit more than 94 GiB!) is constant among many of these crashes, even over different SBCL versions.
The message "no size function for object at..." varies between SBCL and/or QEMU versions, however.
I also just noticed that the memory address of the object in question is in unmapped space.
I will keep poking at this, hopefully I'll eventually come up with a test case that's useful for QEMU devs.
Thank you for the fast response!
Re QEMU, I was afraid so. :-(
The number 100940122304 (actually a bit more than 94 GiB!) is constant among many of these crashes, even over different SBCL versions.
The message "no size function for object at..." varies between SBCL and/or QEMU versions, however.
I also just noticed that the memory address of the object in question is in unmapped space.
I will keep poking at this, hopefully I'll eventually come up with a test case that's useful for QEMU devs.