[lldb] Fix macOS Ventura version number checksUnlike Python 2 which reports 10.16 on any recent macOS, Python 3correctly reports Ventura as macOS 13.
[lldb] XFAIL TestVSCode_breakpointEvents.py on VenturaTestVSCode_breakpointEvents.py is failing on macOS Ventura because wereceive 3 breakpoint events instead of one. This is likely the result of
[lldb] XFAIL TestVSCode_breakpointEvents.py on VenturaTestVSCode_breakpointEvents.py is failing on macOS Ventura because wereceive 3 breakpoint events instead of one. This is likely the result ofdyld moving into the shared cache.
show more ...
[lldb][tests] Automatically call compute_mydir (NFC)Eliminate boilerplate of having each test manually assign to `mydir` by calling`compute_mydir` in lldbtest.py.Differential Revision: https://r
[lldb][tests] Automatically call compute_mydir (NFC)Eliminate boilerplate of having each test manually assign to `mydir` by calling`compute_mydir` in lldbtest.py.Differential Revision: https://reviews.llvm.org/D128077
Revert "[lldb-vscode] Emit the breakpoint changed event on location resolved"This reverts commit 1f21d488bd79a06c9cf405cc5db985fcd71c4f70.
[lldb-vscode] Emit the breakpoint changed event on location resolvedVSCode was not being informed whenever a location had been resolved (after being initated as non-resolved), so even though it was
[lldb-vscode] Emit the breakpoint changed event on location resolvedVSCode was not being informed whenever a location had been resolved (after being initated as non-resolved), so even though it was actually resolved, the IDE would show a hollow dot (instead of a red dot) because it didn't know about the change.Differential Revision: https://reviews.llvm.org/D96680
[lldb] Convert assertTrue(a == b) to assertEqual(a, b)Convert `assertTrue(a == b)` to `assertEqual(a, b)` to produce better failure messages.These were mostly done via regex search & replace, wit
[lldb] Convert assertTrue(a == b) to assertEqual(a, b)Convert `assertTrue(a == b)` to `assertEqual(a, b)` to produce better failure messages.These were mostly done via regex search & replace, with some manual fixes.Differential Revision: https://reviews.llvm.org/D95813
Fix e796c77b26acab0b530ac6516f1dda21b8494733Failure:http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake/14556/testReport/junit/lldb-api/tools_lldb-vscode_breakpoint-events/TestVSCode_breakpoi
Fix e796c77b26acab0b530ac6516f1dda21b8494733Failure:http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake/14556/testReport/junit/lldb-api/tools_lldb-vscode_breakpoint-events/TestVSCode_breakpointEvents_py/Diff:[lldb-vscode] Correctly return source mapped breakpoints for setBreakpoints requesthttps://reviews.llvm.org/D76968It failed a test TestVSCode_breakpointEvents that only runs Darwin that needed to be updated to match the current logic.The change is simple.
[lldb] NFC: Fix trivial typo in comments, documents, and messagesDifferential Revision: https://reviews.llvm.org/D77460
[lldb] Remove accidentally checked-in debugging code
Fix buildbots by disabling this new test until I can fix it.This tests works on Darwin. I will need to check windows and linux.
Stop emitting a breakpoint for each location in a breakpoint when responding to breakpoint commands.Summary: The VS Code DAP expects on response for each breakpoint that was requested. If we respon
Stop emitting a breakpoint for each location in a breakpoint when responding to breakpoint commands.Summary: The VS Code DAP expects on response for each breakpoint that was requested. If we responsd with multiple entries for one breakpoint the VS Code UI gets out of date. Currently the VS code DAP doesn't handle one breakpoint with multiple locations. If this ever gets fixed we can modify our code.Reviewers: labathSubscribers: lldb-commitsTags: #lldbDifferential Revision: https://reviews.llvm.org/D73665