21:39:08drmeisterI found an alternative way to get the arguments from the stack that doesn't mess with the garbage collector.
21:40:15drmeisterI'm sorry this is taking so long. I've had to really get in the weeds of how things like stack frames, object files, dynamic libraries and executables are laid out on macOS and linux.
3:38:25drmeisterYeah - on the stack. Their headers and vtable pointers are gone.
3:38:56Bikewell, cc_stack_enclose just writes the thing into the provided i8 array
3:39:37Bikei don't think we've seen any problems with stack allocated closures not being full objects
3:40:32drmeisterI know. I added them to the new backtraces as afterthoughts - thinking we would find a use for them later.
3:41:03drmeisterBut when I print the backtrace frame structs the stack allocated closures are blowing up the printer.
3:41:42drmeisterI wonder if we are obliterating them somehow and have never noticed .
3:42:09Bikei don't think we do anything special with them
3:42:15Bikelike as far as lisp is concerned they're just objects
3:43:01drmeisterAgreed. They should have a header and a vtable. But I don't see it when I dump them when they should be sitting on the stack perfectly formed.
3:53:44drmeisterAre we allocating enough space for them?