-
Notifications
You must be signed in to change notification settings - Fork 255
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
SourceMaps stopped working for bazel-built processes on version 1.11.2 and 1.11.3 #1228
Comments
Here's my bet on where the problem could be: v1.11.1...v1.11.2#diff-14b183725ee1b7204a41e6600c42c555845df6c5e7ead8bc4705c96c26bc4f90R278 |
Changing the lldb library didn't make a difference, so it points the problem is somewhere in the adapter. I also tried dumping the merged object in |
I'm not familiar with this syntax. Did you mean Try dumping the effective source map via |
in 1.11.1 I get (somewhat redacted):
Here's some more information. Adding Regarding the |
Regarding the logging information, here's the relevant part (again with some paths redacted) which shows that it can't resolve breakpoints:
|
I can't reproduce your problem. The following config works for me: {
"name": "Attach by pid",
"type": "lldb",
"request": "attach",
"sourceMap": { "/proc/self/cwd": "${workspaceFolder}" },
"pid": 2515521
} After attaching the source map is set as expected. Can you try a similar simple config on your end? |
I find this problem on v1.11.3 too: source-map in settings.json is not working(after launching, I typed 'settings show target.source-map' dumps empty). |
@Penguinang can you share your launch configuration? Or, better yet, a verbose log? |
OS: Ubuntu
VSCode version: 1.96.4
CodeLLDB version: 1.11.2
Compiler: clang 14
Debuggee: ELF x64 binaries on Linux with glibc 2.35
When debugging our bazel targets, in version 1.11.2 (or 1.11.3), our sourceMap from
"/proc/self/cwd"
to"${workspaceFolder:code_root_folder}"
stopped working meaning that breakpoints are no longer hit. The same configuration works with version1.11.1
and older. Seems some regression was introduced in 1.11.2, but I can't quite put my finger on it looking at v1.11.1...v1.11.2UPDATE: It seems to affect only requests of type
"attach"
."launch"
configurations are not affected by the regression.The text was updated successfully, but these errors were encountered: