[elephant-devel] [PATCH] Proper deadlock detection for BDB

[Ian Eslick]

Does this require BDB 4.7?  As I recall, conflict detection used to  
require a separate process to run correctly but there was a change in  
4.6 or 4.7 to allow you to do this in the same process.

Also, isn't it true that a true deadlock in a given thread will cause  
the process to lock up if it's not using OS threads (like Allegro  
which will freeze up entirely when a C call fails to return)?  SBCL  
shouldn't have this problem.  Neither of these solutions will work, so  
we should keep around the external process model for these settings.   
This used to drive me nuts when I was developing Elephant on Allegro.

I can dig back into this to refresh my memory unless you are confident  
you're up to speed.

Thanks,
Ian

On Sep 23, 2008, at 9:13 AM, Leslie P. Polzer wrote:

> Fixed a small glitch.
> Updated version attached.
>
> -- 
> LinkedIn Profile: http://www.linkedin.com/in/polzer
> Xing Profile: https://www.xing.com/profile/LeslieP_Polzer
> Blog: http://blog.viridian-project.de/<bdb-deadlock- 
> detect.darcspatch>_______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel