Community
Participate
Working Groups
I am not sure which version of GDB this may have stopped working, but in GDB 7.12+ the code that handles this in CDT does not work anymore. As a result the "record" is never sent to gdb, meaning that reverse-next does not work. A bunch of tests for this are disabled in the DSF-GDB suite. Reduced steps to reproduce: 1) Create a project with a target that support reverse debugging. 2) Check the Enable reverse debugging in the launch configuration 3) Debug the project - it will stop on main 4) click next a few times 5) in the console - type reverse-next That won't work. So, in the console type "record" and then next and reverse-next and it should be working. This stopped working because the logic around the special breakpoint to insert to enable record is not being triggered. It probably is the case that in older gdbs the breakpoint was triggered, even though it was on the same line as the main breakpoint.
New Gerrit change created: https://git.eclipse.org/r/c/cdt/org.eclipse.cdt/+/179128
New Gerrit change created: https://git.eclipse.org/r/c/cdt/org.eclipse.cdt/+/179129
Gerrit change https://git.eclipse.org/r/c/cdt/org.eclipse.cdt/+/179129 was merged to [master]. Commit: http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=554bf844d508ba2e33ca9df291fd73f1ce6c8d7d
Gerrit change https://git.eclipse.org/r/c/cdt/org.eclipse.cdt/+/179128 was merged to [master]. Commit: http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=549b9d00c08a7341d388bd4eafc8b2c9b8813f57