Replies: 2 comments
-
One thing that stands out is that in the first case file paths use Windows notation (drive letter and backslashes), while in the second it's Unix notation. Which notation is used in the debug info? If they are mismatched, lldb may be unable to match path in the breakpoint set request to that in the debug info. |
Beta Was this translation helpful? Give feedback.
-
I tried all the variations (forgot to mention this):
lldb-vscode accepts and verifies both: same executable is used in both debuggers, different results |
Beta Was this translation helpful? Give feedback.
-
OS: Windows 10
VSCode version: N/A
CodeLLDB version: Latest 1.7
Compiler: clang using MSYS (from the clang64 repo)
Debuggee: C++
CodeLLDB is unable to resolve breakpoints
I have a simple 1 file test program compiled with debugging symbols using clang++ on Windows.
codelldb is unable to resolve breakpoints, unless its a function breakpoint
the same code, using
lldb-vscode
works as expected.CodeLLDB:
lldb-vscode:
this seems like something trivial and I must be missing something here
any hint is appreciated
Thanks
Beta Was this translation helpful? Give feedback.
All reactions