Open drandall-microsoft opened 6 months ago
Are you using gcc
to compile the native code for the app? This extension currently use lldb debugger, not sure how well it works with debug symbols in other formats.
Looks like it's using Clang++ in toolchains/llvm
Did a quick search, and seems like lldb should support .so.dbg files as well. Need to debug further on why lldb is not resolving the symbols file.
You can enable lldb logs to see what lldb is doing, in case that can give any hints.
Apologies for the slow response. I'm not sure how to enable the lldb logs (I found this(https://github.com/vadimcn/codelldb/wiki/LLDB-Logging), but didn't see an obvious way to add it to the task). I have put up a minimal-ish repo with my setup (and .vs files in the readme) here: https://github.com/dstbstr/HelloAndroid/tree/main
I've been trying to debug a native-activity sample project. As far as I can tell, the debugger attaches, but I can't hit any breakpoints. Here is a copy of my launch configuration
The symbolSearchPath example lists
"${workspaceFolder}/app/build/intermediates/cmake/debug/obj/${command:abi}/
but my intermediates folder doesn't contain a cmake folder. My outputs/native-debug-symbols/debug just contains a native-debug-symbols.zip. I tried unzipping that, which provided the ABI folders, and I just hard coded it to x86_64. The only file in that folder is libMinimalist.so.dbg which I don't know if that is supported.Here is my Debug Console Log
And in the LogCat I can see that a debugger has connected
Let me know what other information