IMO, timeouts are a band-aid solution: do you really
prefer a stuttering UI to a frozen one. I have to admit
though sometimes even band-aids are useful ;-)
Cheers,
Pawel
On 07/17/2012 10:22 AM, Andy Jin wrote:
Some users report the debug session hangs the IDE.
The stack trace is copied below. At that stage, "gdb"
hangs for some unknown reason (that will be looked at
separately), but the stack trace shows DSF GDB is
waiting for gdb infinitely and that hangs the main UI
thread.
The
org.eclipse.cdt.dsf.gdb.internal.ui.actions.GdbConnectCommand.canConnect()
method sends the connect query using the
org.eclipse.cdt.dsf.concurrent.Query.get() method. The
"get()" method is blocked with no timeout. There is
another "get(timeout, timeoutUnit)" method but it is not
used.
In fact, I see almost all DSF-GDB classes use the
"get()" method, e.g. GdbLaunchDelegate. In the case when
gdb hangs, those methods will block. Is there any reason
we don't use the "get(timeout, timoutUnit)" method?
Thanks,
Andy
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/cdt-dev