Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to resolve liblldb symbols on MacOS #1229

Closed
lichenmike opened this issue Feb 1, 2025 · 7 comments
Closed

Unable to resolve liblldb symbols on MacOS #1229

lichenmike opened this issue Feb 1, 2025 · 7 comments

Comments

@lichenmike
Copy link

lichenmike commented Feb 1, 2025

OS: MacOS 15.2, Darwin x64 24.2.0
VSCode version: 1.96.4
CodeLLDB version: 1.11.3
Compiler: Clang 12.0.0 x86_64 apple darwin 24.2.0
Debuggee: MacOS executable

Debug session crashes at launch due to missing symbols.

Related bug: #1221

Verbose log
  
Verbose logging: on  (Use "lldb.verboseLogging" setting to change)
Platform: darwin x64
Initial debug configuration: {
  name: 'Debug My App',
  type: 'lldb',
  request: 'launch',
  program: '${workspaceFolder}/build/my-app',
  cwd: '${workspaceFolder}',
  __configurationTarget: 6
}
Resolved debug configuration: {
  name: 'Debug Lichen Tracker',
  type: 'lldb',
  request: 'launch',
  program: '${workspaceFolder}/build/my-app',
  cwd: '${workspaceFolder}',
  __configurationTarget: 6,
  terminal: 'integrated',
  expressions: 'native',
  relativePathBase: '/Users/mb/Repos/projects/my-app',
  _adapterSettings: {
    displayFormat: 'auto',
    showDisassembly: 'auto',
    dereferencePointers: true,
    suppressMissingSourceFiles: true,
    evaluationTimeout: 5,
    consoleMode: 'commands',
    sourceLanguages: null,
    scriptConfig: {},
    terminalPromptClear: null,
    evaluateForHovers: true,
    commandCompletions: true,
    reproducer: false
  }
}
Launching adapter
liblldb: /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/LLDB
environment: {}
settings: { evaluateForHovers: true, commandCompletions: true }
[ERROR codelldb] Unable to resolve liblldb symbols: "dlsym(0x452cdc70, _ZN4lldb10SBDebugger14GetBroadcasterEv): symbol not found"
Error: "\"dlsym(0x452cdc70, _ZN4lldb10SBDebugger14GetBroadcasterEv): symbol not found\""
Debug adapter exit code=1 (0x1), signal=null.
@lichenmike lichenmike changed the title Unable to resolve liblldb symbols Unable to resolve liblldb symbols on MacOS Feb 1, 2025
@vadimcn
Copy link
Owner

vadimcn commented Feb 1, 2025

What is the version of your LLDB? I think it might be too old.

@lichenmike
Copy link
Author

Executable appears to reside at /usr/bin/lldb, which returns a version string of:
Apple Swift version 5.3.2 (swiftlang-1200.0.45 clang-1200.0.32.28)

Somewhere along the way the library path was set to the CommandLineTools version at /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework...

I've cleared out this extension's "Lldb: Library" setting so that it now uses the included LLDB which seems to work. CodeLLDB Log output is now showing...

<Various settings here>
  }
}
Launching adapter
liblldb: /Users/mrbynum/.vscode/extensions/vadimcn.vscode-lldb-1.11.3/lldb/lib/liblldb.dylib
environment: {}
settings: { evaluateForHovers: true, commandCompletions: true }
[DEBUG codelldb] Connecting to 127.0.0.1:64776
[DEBUG codelldb] New debug session
[DEBUG codelldb::dap_codec] --> {"command":"initialize","arguments":{"clientID":"vscod...

@andres1138
Copy link

I am also dealing with this issue, it is incredibly annoying.

@vadimcn
Copy link
Owner

vadimcn commented Feb 1, 2025

@andres1138 Comments such as this one are unhelpful.

@vadimcn
Copy link
Owner

vadimcn commented Feb 1, 2025

@nullsquirrel I assume your issue is now resolved?

@vadimcn
Copy link
Owner

vadimcn commented Feb 1, 2025

@andres1138 I am not taking this as an attack, however your comment did not add any information that would help to advance the discussion.
After a fix in v1.11.3, liblldb ABI compatibility should be back to where it was in v1.11.1. Is this not the case?

@lichenmike
Copy link
Author

Yes, this seems to be resolved. Thanks for the support!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants