microsoft / microsoft/vscode-cpptools
MacOS 15.4 M1 Error while trying to enter break state. Debugging will now stop. LLDB exited unexpectedly with exit code 139
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
After update OS to 15.4. (and autoupdate Xcode) crash debug process on breakpoint (application not crash). Crash corresponding with mouse action in application (if same action activate from keyboard not crash debug). First breakpoint maybe work. crash on 1, 2 or 3-d of iteration same breakpoint
MacOS Sequoia 15.4. arm M1
VSCodeVersion: 1.99.2 (Universal)
Commit: 4949701c880d4bdb949e3c0e6b400288da7f474b
Date: 2025-04-10T01:21:25.295Z
Electron: 34.3.2
ElectronBuildId: 11161073
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.4.0
lldb -version
lldb-1700.0.9.46
Apple Swift version 6.1 (swiftlang-6.1.0.110.21 clang-1700.0.13.3)
clang --version
Apple clang version 17.0.0 (clang-1700.0.13.3)
Target: arm64-apple-darwin24.4.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
cmake version 3.30.2
use wxWidgets 3.2.6
1: (85258) Send Event AD7MessageEvent
--> E (output): {"type":"event","event":"output","body":{"category":"stderr","output":"ERROR: Error while trying to enter break state. Debugging will now stop. LLDB exited unexpectedly with exit code 139 (0x8B).\n"},"seq":8755}
ERROR: Error while trying to enter break state. Debugging will now stop. LLDB exited unexpectedly with exit code 139 (0x8B).
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (85259) Send Event AD7ProgramDestroyEvent\n"},"seq":8757}
full log:
{
"name": "mac c++",
"type": "cppdbg",
"request": "launch",
// Resolved by CMake Tools:
"program": "${command:cmake.launchTargetPath}",
"args": [],
"additionalSOLibSearchPath": "${workspaceFolder}/build/RESULT",
"stopAtEntry": false,
"cwd": "${workspaceFolder}",
"environment": [
{
// add the directory where our target was built to the PATHs
// it gets resolved by CMake Tools:
"name": "PATH",
"value": "${env:PATH}:${command:cmake.getLaunchTargetDirectory}"
},
{
"name": "OTHER_VALUE",
"value": "Something something"
}
],
"logging":
{
"engineLogging": true,
"trace": true,
"traceResponse": true
},
"externalConsole": false,
"MIMode": "lldb"
},
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached lldb-log.txt and the supplied mac C++ launch configuration, then reproduce the breakpoint failure on macOS 15.4 with an M1 and compare mouse-triggered and keyboard-triggered actions. Done means the LLDB exit can be consistently reproduced and its responsible component is identified or the breakpoint iteration no longer terminates debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp, macos, vscode
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100