From: <no...@so...> - 2002-12-29 12:18:04
|
Feature Requests item #612513, was opened at 2002-09-21 16:45 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=360894&aid=612513&group_id=10894 Category: 80. Thread Package Group: None Status: Open Resolution: None Priority: 5 Submitted By: Markus Elfring (elfring) Assigned to: Zoran Vasiljevic (vasiljevic) Summary: Detect deadlocks with TCL Initial Comment: I've read under "http://java.sun.com/j2se/1.4.1/changes.html#vm" about a utility that can detect deadlocks with the programming language "Java". (Example listing: http://java.sun.com/j2se/1.4.1/sample-output.html) Can a similar tool be offered for the programming language "TCL"? ---------------------------------------------------------------------- >Comment By: Markus Elfring (elfring) Date: 2002-12-29 13:18 Message: Logged In: YES user_id=572001 4. Another solution: A detection is not needed if a system was created deadlock free. (http://groups.google.com/groups?dq=&start=150&hl=de&lr=&ie=UTF- 8&group=comp.hypercube&selm=302%40hubcap.UUCP) ---------------------------------------------------------------------- Comment By: Markus Elfring (elfring) Date: 2002-12-29 00:53 Message: Logged In: YES user_id=572001 3. Is there anything different with "Java-platform-level deadlocks" compared to "Tcl-platform-level deadlocks"? What are the internal programming interfaces? ---------------------------------------------------------------------- Comment By: Markus Elfring (elfring) Date: 2002-12-28 22:58 Message: Logged In: YES user_id=572001 Damned - The pthread interface does not offer any function to query the thread and lock usage. 1. I am wondering now why this was not introduced into POSIX 1003.1c after this standard was available for so many years. 2. I'm curious for your TIP. I hope that the TCL community will find an other function library to retrieve the requested information. ---------------------------------------------------------------------- Comment By: Zoran Vasiljevic (vasiljevic) Date: 2002-12-28 19:40 Message: Logged In: YES user_id=95086 Detecting deadlock may be done be wrapping the mutex API i.e. providing your own set of mutex operations. This would, however, slow down the application. I might put this into the TIP I'm preparing about the Tcl threading API. This may be then conditionaly compiled for debugging purposes. ---------------------------------------------------------------------- Comment By: Markus Elfring (elfring) Date: 2002-12-28 12:39 Message: Logged In: YES user_id=572001 The solution will be somewhere in the lock APIs. (http://docs.sun.com/db/doc/806-6867/6jfpgdcml?a=view) ---------------------------------------------------------------------- Comment By: Markus Elfring (elfring) Date: 2002-09-21 17:18 Message: Logged In: YES user_id=572001 This tool will need some functions in the thread interface to query the dependencies between the running or waiting threads. A helpful function would be to return a list of identifiers for deadlocked threads. I suggest to offer the function "thread::is_deadlocked id", too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=360894&aid=612513&group_id=10894 |