[LLDB] Improve the logging output from InstrumentationRuntimeBoundsSafety plugin (#175082)
This change makes several improvements:
* Adds some additional logging in the
`InstrumentationBoundsSafetyStopInfo` constructor. In particular logging
is now emitted along the success path so we can see what the plugin
computed.
* `ComputeStopReasonAndSuggestedStackFrame` now logs if the debug info
vs no debug info path is taken.
* `CheckIfRuntimeIsValid` now prints the correct module path. Previously
it always printed `<unknown module>`.
* `Deactivate` now prints the breakpoint number correctly. Previously
this would try to print signed breakpoints IDs as unsigned. This problem
was observable because internal breakpoints use negative breakpoint IDs.
rdar://167797706
GitOrigin-RevId: 631645cae8dcaa3d0521e12dcc2ff81087494358
1 file changed