Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 572742 - Reverse debugging at startup does not always work
Summary: Reverse debugging at startup does not always work
Status: RESOLVED FIXED
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: Next   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 10.3.0   Edit
Assignee: Jonah Graham CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-09 16:02 EDT by Jonah Graham CLA
Modified: 2021-04-10 12:33 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jonah Graham CLA 2021-04-09 16:02:46 EDT
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.
Comment 1 Eclipse Genie CLA 2021-04-09 16:06:23 EDT
New Gerrit change created: https://git.eclipse.org/r/c/cdt/org.eclipse.cdt/+/179128
Comment 2 Eclipse Genie CLA 2021-04-09 16:06:24 EDT
New Gerrit change created: https://git.eclipse.org/r/c/cdt/org.eclipse.cdt/+/179129