Detecting deadlocks in interop-debugging

Details Detecting deadlocks in interop-debugging Detecting deadlocks in interop-debugging

2011-03-29

2011-03-29

Zhen, Li B (Department: 2194)

Electrical computers and digital processing systems: virtual mac

Task management or control

Process scheduling

Reexamination Certificate

active

07917909

ABSTRACT:
A method and system for implementing detecting deadlocks in interop-debugging is described herein. One or more synchronization objects that an application program interface (API) could block on are identified. A canary thread that takes one or more of the synchronization objects is created. The canary thread is called to take the one or more synchronization objects. If the canary thread returns within a predetermined timeout period, then the one or more synchronization objects are available and safe to take. If the canary thread does not return within the predetermined timeout period, then the one or more synchronization objects may not be available.

REFERENCES:
patent: 2004/0139386 (2004-07-01), Ishimura et al.
patent: 2007/0143766 (2007-06-01), Farchi et al.
Carver Richard H., Yu Lei, A general model for reachability testing of concurrent programs, Nov. 8-12, 2004, Springer Berlin / Heidelberg, vol. 3308/2004, p. 76-98.
Robert Ian Oliver, Designing Enterprise Applications with Microsoft Visual Basic .NET, Microsoft Press; 1 edition (Oct. 16, 2002), p. 308.

Affiliated with

Also associated with

Rating

Detecting deadlocks in interop-debugging does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Detecting deadlocks in interop-debugging, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Detecting deadlocks in interop-debugging will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-2761413