On Mon, 7 May 2007 14:52:27 -0600, "Vladimir Sedach" vsedach@gmail.com wrote:
While debugging a web application, the need to not catch errors became apparent. Unfortunately, there are spurious stream errors that make this less than useful currently (someone has informed me that this problem is well known). The attached patch is my proposal to let people deal with this and take advantage of (setf *catch-errors-p* nil).
I had thought that the changes in 0.9.0 made the spurious time-out errors go away. Are you using the newest version? Which errors do you see exactly? Can you send a backtrace?
If you think this is the wrong way of going about things, please let me know.
If this is really still a problem, I'd like to release a patch for all supported implementations.
Thanks, Edi.