20:01:46clothespinhi. can anyone tell me what causes a memory_fault_emulation_trap? it seems to be set off by construction of a clos instance, but that's alll i know.
20:07:49phoeclothespin: any more context on that issue? how did you end up getting it?
20:09:35clothespinwell when i run without a debugger (gdb/linux) I get a signal 8 floating point error, so when i run the steps through gdb I get the memory fault trap, and nicely sbcl spit out a lisp backtrace saying it was trying to make a particular clos object
20:10:22clothespini'm using swiftshader cpu vulkan implementation and this is vktk code which creats a render pass
20:15:18clothespingoogle says sig 8 is usually an out of bounds reference
20:15:43clothespincould i have clobbered some lisp heap?
20:27:23ShinmeraC code will routinely cause floating point exceptions.
20:28:03ShinmeraYou should use something like float-features:with-float-traps-masked to disable them during C code that is relying on NaN/INF coercion.
20:28:04clothespini'm masking those, but somehow this signal kills the lisp