BreakpointManager: Adjust breakpoint installation logic.
If the debugger interface isn't currently connected, don't attempt to actually install the breakpoint, and simply consider the operation a success. This allows setting new breakpoints after e.g. the team has exited. Resolves remaining part of #9774.
This commit is contained in:
parent
6443c430b2
commit
cebb446f55
@ -494,8 +494,13 @@ BreakpointManager::_UpdateBreakpointInstallation(Breakpoint* breakpoint)
|
||||
|
||||
if (shouldBeInstalled) {
|
||||
// install
|
||||
status_t error = fDebuggerInterface->InstallBreakpoint(
|
||||
breakpoint->Address());
|
||||
status_t error = B_OK;
|
||||
// if we're not actually connected to a team, silently
|
||||
// allow setting the breakpoint so it's saved to settings
|
||||
// for when we do connect/have the team in the debugger.
|
||||
if (fDebuggerInterface->Connected())
|
||||
fDebuggerInterface->InstallBreakpoint(breakpoint->Address());
|
||||
|
||||
if (error != B_OK)
|
||||
return error;
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user