Community
Participate
Working Groups
As is available since CDT 8.0.0 debug views expressions, registers, variables and memory browser can be pinned to a specific debug context. This has many amazing advantages when debugging multiple programs at once. Unfortunately the debug breakpoints view and the memory view currently do not have this capability. It would be great to have this. When debugging two programs using the same sources a very common use case is to set a breakpoint for one debug session that needs to be ignored by another debug session. Pinning breakpoints to debug context would allow this.
The Memory view comes from Platform Debug, unfortunately Platform Debug doesn’t have Pin&Clone support. For the Breakpoints view, I don’t think Pining will help. What you really want is to be able to set the breakpoint for the selected session (thread, process) and not the other debug session. This needs to be handled in the CDT breakpoint manager. Pinning is a way for the view to ignore debug context change event, i.e don’t follow the selected debug context. It probably will work if it is used together with the “Show Breakpoint Supported by Selected Target” action. When pin is enabled, this action has to be enabled as well.
(In reply to comment #1) > For the Breakpoints view, I don’t think Pining will help. What you really want > is to be able to set the breakpoint for the selected session (thread, process) > and not the other debug session. This needs to be handled in the CDT breakpoint > manager. Pinning is a way for the view to ignore debug context change event, > i.e don’t follow the selected debug context. It probably will work if it is > used together with the “Show Breakpoint Supported by Selected Target” action. > When pin is enabled, this action has to be enabled as well. See discussion in https://bugs.eclipse.org/bugs/show_bug.cgi?id=360735
