Community
Participate
Working Groups
This bug is meant to track any changes that will be required to support GDB 7.2. Normally, there should be none, as GDB should be backwards compatible, but in practice, this may not always be the case. Once GDB 7.2 is released officially we'll be able to tell if any changes are needed as part of this bug.
Created attachment 171116 [details] Fix for =thread-group-created changed to =thread-group-started Currently, GDB HEAD has a non-backwards-compatible change that makes the event "thread-group-created" change to "thread-group-started". This change may or many not remain in GDB. Discussions are still ongoing: http://sourceware.org/ml/gdb/2010-06/msg00016.html This patch updates the DSF-GDB code to handle this, if the change is retained. We should only commit this patch if when we know if GDB will keep the change or not.
I've committed the patch for the new name "=thread-group-started". It will be part of GDB 7.2
*** cdt cvs genie on behalf of mkhouzam *** Bug 315796: Support for GDB 7.2 where the MI event "=thread-group-created" has been replaced with "=thread-group-started". We need to keep both to support older GDBs. [*] MIRunControlEventProcessor_7_0.java 1.11 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/mi/service/command/MIRunControlEventProcessor_7_0.java?root=Tools_Project&r1=1.10&r2=1.11 [*] GDBProcesses_7_0.java 1.25 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/gdb/service/GDBProcesses_7_0.java?root=Tools_Project&r1=1.24&r2=1.25
Committed patch to the 7_0 branch as well.
*** cdt cvs genie on behalf of mkhouzam *** Bug 315796: =thread-group=created has been replaced by =thread-group-started in GDB 7.2. We need to handle both cases to support older GDBs as well. [*] GDBProcesses_7_0.java 1.21.2.2 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/gdb/service/GDBProcesses_7_0.java?root=Tools_Project&r1=1.21.2.1&r2=1.21.2.2 [*] MIRunControlEventProcessor_7_0.java 1.10.2.1 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/mi/service/command/MIRunControlEventProcessor_7_0.java?root=Tools_Project&r1=1.10&r2=1.10.2.1
Created attachment 179594 [details] Use proper version number for GDB 7.2 Now that GDB 7.2 has been released, we can use the "7.2" version name. Committed to HEAD and 7_0.
*** cdt cvs genie on behalf of mkhouzam *** Bug 315796: Use proper "7.2" version string for GDB 7.2 [*] GdbDebugServicesFactory.java 1.14 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/gdb/service/GdbDebugServicesFactory.java?root=Tools_Project&r1=1.13&r2=1.14 [*] GdbDebugServicesFactory.java 1.11.2.1 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/gdb/service/GdbDebugServicesFactory.java?root=Tools_Project&r1=1.11&r2=1.11.2.1
The last issue that is left, is to fix the JUnit tests when using GDB 7.2. It is the Registers tests that fail because the new GDB list more registers than before.
I've opened Bug 326878 to track the last issue, so we can close this bug.
