Community
Participate
Working Groups
GDB doesn't support reverse debugging when non-stop mode is enabled. Currently, if both are selected in the debug configuration page, reverse debugging won't work and nothing is done to inform the user about this. This is confusing for users who are not familiar with those features (like me!). I suggest disabling the Reverse debugging check box and setting its value to false when Non-stop is checked. That way, the user will not expect the reverse debugging to work.
Created attachment 155946 [details] Disable reverse debugging if non-stop is checked Patch for 6.0.2 and 6.1 (aka 7.0).
Thanks. My worry about this solution is that I wonder why we prioritize non-stop over reverse? For example, if the user selects reverse first, why don't we disable non-stop? Maybe also adding a string to explain why the text box is disabled. I can see getting questions about the reverse checkbox being disabled just as much as the reverse toggle button.
Created attachment 157718 [details] Improved patch Thanks for the comments, this patch should be better.
Marc, do you still think this is a good idea? If so, I can update the patch. If not, I will mark this as INVALID.
Thinking about it some more I got to thinking this patch would cause a problem if GDB ever does support reverse and non-stop. The limitation is not from CDT but from GDB. Say GDB 7.4 does support reverse and non-stop, then we won't have a solution that will work for both GDB 7.4 and older GDBs. One thing we should use more are notifications to the user when something fails. How about a warning dialog when the launch session is started and we confirm that the GDB version used does not support both options? Or is that not user friendly enough?
Adding me to the list of non familiar users, I was quite puzzled on why the reverse debugging toggle button is disabled and did not figure out it was related to the settings of non-stop mode, can this e.g. be reflected in the tooltip of the toggle button ?
New Gerrit change created: https://git.eclipse.org/r/67498
New Gerrit change created: https://git.eclipse.org/r/67499
(In reply to Marc Khouzam from comment #5) > How about a warning dialog when the launch session is started and we > confirm that the GDB version used does not support both options? The following patch does that; which is to pop-up a dialog and fail the session. > New Gerrit change created: https://git.eclipse.org/r/67498
(In reply to Eclipse Genie from comment #8) > New Gerrit change created: https://git.eclipse.org/r/67499 The above patch add a dialog warning when a breakpoint is hit which has an action to enable/disable reverse debugging but fails to do it (e.g., if it is a non-stop session).
