7:30:42ShinmeraAnother Windows thing: sometimes the stack trace appears completely useless, consisting merely of a few frames of SB-KERNEL:INTERNAL-ERROR above two foreign function frames. Makes figuring out what the heck the error was very, very difficult.
7:31:24ShinmeraI know the error is somewhere in lisp land thanks to the restarts that are active
8:59:03luisShinmera: the problem, I think, is that the win64 calling convention omits the frame pointer so we need to call CaptureStackBackTrace or something similar which knows how to map <instruction addresses> to <stack pointer offsets to the frame base> essentially