[cdt-debug-dev] Remove timeouts in CDT?

[Øyvind Harboe <oyvind.harboe@xxxxxxxxx>]

>I do not understand what must be fix in the CDT, if gdb stops responding
>for x number of reason, what exactly do you propose ?

Kill the process.

CDT already has a tiny amount of native code per platform.

>> Assuming that CDT was changed to always be able to terminate a GDB
>> session, would you agree that the timeout should be removed?
>> 
>
>it's not like we can do in Java
>	signal(SIGKILL, 0);
>On some system gdb does not respond, to events/signals.

If I understand you correctly, then it would be necessary to add a "kill process" 
to the CDT native code library. 

No big deal, or?

Using the "kill" command on Linux and even CygWin is an alternative to
adding native code. How to launch the "kill" command would presumably be
platform dependant.

>Well there are 2 timeouts when launching and in normal operation.

If terminate worked always, it seems to me that both could be removed.

>On that subject there is a new Architecture that will be part of
>Eclispe-3.1 that we intend to take full advantage of, please read:
>
>http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-debug-home/r3_1/docs/concurrency/Concurrency-Debug.html?rev=HEAD&content-type=text/html
>
>Altough I still think timeout will be a necessacity, to be able to
>"bail out" from a long running operation.

I skimmed through it, but my understanding of the CDT innards isn't sufficient
to properly connect the issues to the timeout discussion above.


-- 
Øyvind Harboe
http://www.zylin.com