|
From: Dexter A. <ve...@ia...> - 2003-04-07 00:00:38
|
I spent some time this afternoon trying to get a simple debug plug-in running in eclipse that could create an event when a thread locked an object. Unfortunately, I wasn't having much luck-- some functionality isn't as directly available as I'd like (such as being forced to use break points on method entry to catch locks, rather than an explicit event), but worse, now that I've been playing with it some, I'm running into IJavaDebugTarget.supportsMonitorInformation() always returning false! Ie, this JVM (Sun's 1.4 on Win32) doesn't work for tracing monitors with eclipse. To test it, I tried playing with the "Threads and Monitors" debugging view, and it has the same problem. This is clearly bad. :-( At this point, I'm more-or-less abandoning the plan of integrating tightly within the eclipse debugger. I don't mean abandoning eclipse, just that the level of integration will be low-- you can visualize your code from an eclipse menu, but not as part of the normal eclipse debugging. That way, we can drop down to straight JDI calls, which seem to work more reliably. Has anybody made better or different progress on this? Thoughts? -- Brian "Dexter" Allen "Being nationalistic in the sense in which it is www.luminousbeings.com now demanded by public opinion would, it seems ve...@ia... to me, be for us who are more spiritual not mere ve...@ac... insipidity but dishonesty, a deliberate deadening of our better will and conscience." Friedrich Nietzche (1884) |