Debugging: clang/lldb/macOS - no symbols for app but symbols loaded in lldb

Discussed in https://github.com/microsoft/vscode-cpptools/discussions/9867

^{Originally posted by thisisagenericusernameforagenericperson September 9, 2022}
Hello,

I'm trying to use vscode to build and debug an app that uses QT. I get symbol information for QT classes, but not for my own classes.
The data in the "variables" panel only shows memory addresses. However, doing a -exec image lookup -vn MyClassName shows that there are two locations found where the symbol has been found. Curiously, it's the same location twice.
Also, the callstack shows proper symbol names as well.
In any case, this indicates that the symbol is available to the lldb debugger, but not in vscode.

Would love to hear about any suggestions. Thanks!

The following is my launch configuration.

{
"configurations": [
{
"name": "C/C++: Run with Debugger",
"type": "cppdbg",
"request": "launch",
"program": "${workspaceFolder}/${config:buildDirectory}/debug/${config:appName}",
"args": [],
"stopAtEntry": false,
"cwd": "${workspaceFolder}/${config:buildDirectory}/debug",
"environment": [],
"externalConsole": false,
"MIMode": "lldb",
"symbolLoadInfo": {
"loadAll": true,
"exceptionList": "",
},
"preLaunchTask": "Build (Debug)",
"setupCommands": [
{
"text": "settings set target.process.thread.step-avoid-regexp """,
"description": "Enable stepping into STL"
}
],
"logging": {
"engineLogging": false,
"trace": false,
"traceResponse": false
}
}
],
"version": "2.0.0"
}

Start with the linked discussion 9867 and reproduce the macOS LLDB session using the launch configuration in this issue. Compare the Variables panel with -exec image lookup -vn MyClassName and the symbolized call stack; done means the app's own class symbols appear correctly in VS Code variables.