AW: [cdt-dev] Cygwin gdb refuses to be killed

["Ploett, Norbert" <norbert.ploett@xxxxxxxxxxx>]

Hi Virender,

 

testing is easy. Just set up a debug launch configuration with "gdbserver" debugger and "forget" to start the gdbserver. The gdb will report an error after the target-select command and will provoke the pgdb.destroy() command.

 

Note that the bug is already fixed and that the fix will be available in CDT 3.1.2 and 4.0.

 

 

 

Norbert

---

Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Kumar, Virender
Gesendet: Donnerstag, 21. Dezember 2006 11:12
An: CDT General developers list.
Betreff: RE: [cdt-dev] Cygwin gdb refuses to be killed

Hello Norbert

 

This scenario seems quite interesting and relevant for our plug-in (HP C/C++ Remote developer plugin). Our plugin provides a way of doing remote debugging on HP-UX box. For this gdb needs to be installed on the remote system. The code for this plugin has also been submitted to CDT (https://bugs.eclipse.org/bugs/show_bug.cgi?id=168048).

 

We are able to successfully kill remote debug processes. Can you give some test cases to reproduce the problem mentioned in your mail. I would like to try those on our plugin.

 

Regards

Virender.