[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-debug-dev] Remove timeouts in CDT?
|
>
> > IMHO the timeouts should stay. It's possible for GDB, whether through =
> =3D
> > fault of its own or hardware drivers etc., to get in a state where it =3D
> > hangs but you can't seem to kill it.
> >=20
> > That being said, we find it really hard to pick a good timeout. When =3D
> > erasing flash and then loading a large amount of code/data into flash, =
> =3D
> > the default timeouts are sometimes not enough.
>
> I'm of the opinion that it is not practical to point to GDB when CDT is
> unable to terminate a debug session. This must be fixed in CDT.
>
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 ?
> 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.
> Hmmm... perhaps there should be a non-configurable timeout for a
> terminate request of e.g. 5 seconds, after which CDT would simply
> terminate the GDB process.
>
> This is the desired behaviour for embedded applications at least. Does
> CDT support letting a plugin enforce the behaviour described above?
>
Well there are 2 timeouts when launching and in normal operation.
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.
