[cdt-debug-dev] Also Removed from CDT 2.x: Add Address Breakpoint...

["Daryl Spitzer" <DSPITZER@xxxxxxxxxx>]

I should have posted my question to [cdt-debug-dev] in the first place,
but I thought I might as well now...

I wrote:

> ...another menu item from the Run in CDT 1 that was removed from
> CDT 2: "Add Address Breakpoint...".  I suspect that this was removed
> because any user who wants to set a breakpoint by address should be
> comfortable doing so using the GDB console.  In other words, was
> it removed because most users would never use it?  Or were there
> other problems with it?

And Mikhail Khodjaiants replied:

Breakpoints (and watchpoints) in Eclipse are resources shared by all
active 
sessions. When you start a debug session the CDT debugger tries to
filter 
out the breakpoints that don't belong to this session. This is more or
less 
simple for the breakpoints associated with source files or projects. In
this 
case we use the source lookup mechanism. We associate address
breakpoints 
with the corresponding executables.
If there is no filtering criteria (which is the case of the global "Add 
address breakpoint" action) the debugger would try to set address 
breakpoints for all running sessions. This will result in unexpected 
breakpoints and gdb crashes.
That's the main reason why we decuded to remove this action, as well as
the 
"Add Function Breakpoint" action (I could have saved it for the third
beer). You can use the global "Toggle Breakpoint" action. If the
Disassembly view 
is active it works as "Toggle address breakpoint". There is also a ruler

action in the view.

--
Daryl Spitzer
Santa Cruz Technology Center
Altera Corporation
408-544-8539
dspitzer@xxxxxxxxxx