libera/#clasp - IRC Chatlog
Search
1:40:14
bike
mmtk stuff: i'm adding some C++ functions to indicate that a block doesn't touch GC memory. If you enter such a "GC-safe" block the GC can run concurrently with your code. If you don't do that nothing will break but if a GC needs doing every thread will block until the long non-GC code is done. I don't think there's really any way to avoid this
2:16:20
bike
trying to normalize everything has clued me in that snapshot save tries to write to lisp streams while the world is stopped
2:21:33
bike
i guess this means it tries to write to *standard-output*, which could be bound to anything, so it could call arbitrary gray stream code.
3:35:49
drmeister
I'm hitting this problem - I thought we solved this a long time ago. It's spending a lot of time in Unwind_Find_FDE
3:45:43
bike
well the other stuff basically looks like lisp code, so it's probably not throwing C++ exceptions
3:51:05
bike
the main way they'd be happening is if you have lisp calling c++ calling lisp but with the C++ not marked CL_UNWIND_COOP(true). maybe some of those callbacks?