[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Cygwin gdb refuses to be killed
|
Hello Norbert
I think this scenario is not valid for our plug-in.
Gdbserver would normally be used if the machine on which we are running GDB is
different from the machine on which we run the program being debugged. In our
case, the gdb process as well as the program being debugged, runs on the remote
machine.
May I also ask if you are developing your own solution
to enable remote debug. Or are you using some existing tools. What is the
OS platform for which this feature is required.
Regards
Virender.
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
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.
