RE: [cdt-dev] Debugging DSF Request Monitors

[<Ed.Swartz@xxxxxxxxx>]

Hi Jens,

I've found it helpful to put a breakpoint in the catch block of FutureTask#Sync#innerRun().  Throwables can be caught there, bypassing the request monitor machinery of DSF, never to be seen again.

Or, you can enable the platform debug options org.eclipse.cdt.dsf/debug/executor and org.eclipse.cdt.dsf/debug/monitors .  Output goes to ${workspace}/.metadata/trace.log.

-- Ed

-----Original Message-----
From: Elmenthaler, Jens [mailto:jens.elmenthaler@xxxxxxxxxx] 
Sent: Tuesday, March 16, 2010 10:38 AM
To: CDT General developers list.
Subject: [cdt-dev] Debugging DSF Request Monitors

I'm currently having problems that the variables view hangs (after I touched DSF GDB code).

My guess is that some RequestMonitor is not getting its done(), and because of this blocks further updates of the variables view. I already repeatedly reviewed my code changes, but I cannot find something.

I also experimented with tons of debug outputs I generated myself, and the DSF debug options. But still, I'm not getting the hang what is going one.

I wonder if there is a way to find out which currently existing RequestMonitors have not yet received their done(). Together with stack trace created in the RequestMonitor constructor, I should have a hint what hangs.

Jens.