You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to mention a special border case that bit me when debugging a Linux target from a Windows host. Since the build sources were placed in a local Windows directory different from the original Linux build directory, I used the sourceMap option to map between them, as described in: https://github.com/vadimcn/vscode-lldb/wiki/Breakpoints-are-not-getting-hit
The mapping was something like:
"/build/dir/on/linux": "X:/source/dir/on/windows"
Even though the paths were correct, LLDB failed to resolve the symbols to set breakpoints. The problem was due to the mapping containing the drive letter in upper case, while vscode-lldb used lower-case in its breakpoint path, leading to a mismatch in LLDB due to case-sensitive comparison.
By changing to lower-case drive letter in the sourceMap the problem disappeared.
There may be other scenarios leading to the same problem - with case differences - but I haven't investigated further.
It would be nice if something was mentioned about this in the Wiki page, to help other users avoid this problem.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I would like to mention a special border case that bit me when debugging a Linux target from a Windows host. Since the build sources were placed in a local Windows directory different from the original Linux build directory, I used the sourceMap option to map between them, as described in:
https://github.com/vadimcn/vscode-lldb/wiki/Breakpoints-are-not-getting-hit
The mapping was something like:
"/build/dir/on/linux": "X:/source/dir/on/windows"
Even though the paths were correct, LLDB failed to resolve the symbols to set breakpoints. The problem was due to the mapping containing the drive letter in upper case, while vscode-lldb used lower-case in its breakpoint path, leading to a mismatch in LLDB due to case-sensitive comparison.
By changing to lower-case drive letter in the sourceMap the problem disappeared.
There may be other scenarios leading to the same problem - with case differences - but I haven't investigated further.
It would be nice if something was mentioned about this in the Wiki page, to help other users avoid this problem.
Beta Was this translation helpful? Give feedback.
All reactions