slavapestov/factor — comment on commit c536c84c13686c2329baaca883f6b3a851cd6e74
File:  line 0
By slavapestov:

@jckarter When the VM is compiled with DEBUG=1, general_error() triggers a GC. This turns up various interesting bugs. So really you're stuck in a memory protection error loop? Can you get a Factor stack trace at this point from the fep?

Also, should an asynchronous signal from within an FFI call still protect the safepoint, or unwind immediately? The latter can be done safely, because we have callstack state and prepare for signals before making an FFI call. However, you still have to careful if you hit the signal inside the VM -- in particular during GC.