class BreakpointObserver

Indicates that the breakpoint has matched one or more new locations. This could be a result of

creating the breakpoint, updating its settings, or the system automatically detecting new code

that the breakpoint could apply to.

The |user_requested| flag will be set when this event was triggered by a user action like

updating the breakpoint settings. It will be false when the system automatically added the

locations due to dynamic code loading.

If needed the added breakpoint locations could be added to this call.

Breakpoints are installed asynchronously by the backend. If the backend fails to install (or

remove) the breakpoint, this callback will be issued with the error. If the breakpoint applies

to more than one location, some locations could have succeeded even in the presence of this

error.

These backend errors can occur at any time, not just when setting new settings, because new

processes or dynamically loaded shared libraries can always be added that this breakpoint

could apply to.

This callback can also be issued from host-side actions, such as putting a condition on a

breakpoint. Cases such as invalid conditional expressions will also issue this callback.

This will get issued for all breakpoints including internal ones.

The implementation should not delete the breakpoint from within this callback as other

observers may need to be issued and the object will still be on the stack.

Indicates that the breakpoint implicitly updated itself. What specifically was updated is

indicated by |what|.