tree 514201cbb8b02ab3dc39f27ebc421d051954feb1
parent 6041c745f32e8fd60ed24e29e7d919d8d1c87ca6
author Jonas Devlieghere <jonas@devlieghere.com> 1741049781 -0600
committer GitHub <noreply@github.com> 1741049781 -0600
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJnxk+1CRC1aQ7uu5UhlAAAYIYQACzours82yHVf3RVAJubqtKl
 f7vUizmnpYMNltninzonmrl9j5J8JAaMl7cTkmDJBY+vFZCZ1lY+1vgY5Po2VAzg
 bWDyP5MB5yHAgTxkUOJ7vKna9SBZAAH5/evFO8izTOwAaXlK7JzyYM2WBZ1Tv/lc
 GSMOSmbvEmuMadpo1UvZlBZA0ySJ3fqbVEowy04q/iroV+P13yOZU4c871svzjPH
 d0BJjuis/sWdN3bgyWbKqN9tq8f+4hVMF73q5EzvbERLtYkD6jsczXE18tpzZFXo
 PERc2wstmZvvWp8sfbrIQ8AOaJp6fmuk1Ku2284vqiUhwN86vV3N6g7AxGuTMuMw
 yOa+ZttQN9Gl3aBf9czwaznP6lh/WmVMJFby/q77uM/InN52GXiTGL18RQkMdU9U
 Qni4ia9dZDX+2sa8WY9vxh1v8V7T9QKOSSGlwXGVCT5Z7V4VUEU/V7MAwkPXR/qK
 2hmBCwyxdY88xhaPSRLi3f9gT5qD4exuhReQ3uM1jA2geiCAZhKymL2qMIagihIo
 gK1mu3tZZbOBXjXJAnrI2LtEWcJvByWosITbRquwtr10Q3NKcXkZTMf6Laxg4ZPm
 hB8BceMDouJ9xtmrZgbZ7urCkJlil7oElgj82hsUZ8VcRy7WV+wOrSh3jOsJHARG
 64by0BOfNvfg1o1nAew7
 =fsiR
 -----END PGP SIGNATURE-----
 

[lldb-dap] Correctly report breakpoints as resolved on macOS (#129589)

On macOS, breakpoints are briefly unresolved between process launch and
when the dynamic loader has informed us about the loaded libraries. This
information was being forwarded by lldb-dap, but only partially. In the
event handler, we were listening for the `LocationsAdded` and
`LocationsRemoved` breakpoint events. For the scenario described above,
the latter would trigger and we'd send an event reporting the breakpoint
as unresolved. The problem is that when the breakpoint location is
resolved again, you receive a `LocationsResolved` event, not a
`LocationsAdded` event. As a result, the breakpoint would continue to
show up as unresolved in the DAP client.

I found a test that tried to test part of this behavior, but the test
was broken and disabled. I revived the test and added coverage for the
situation described above.

Fixes #112629
rdar://137968318