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
Puting your source code under path like: /home/tester/Documents/test司法
Open in VS Code
Set some BP
F5 tostart debugging
Expected:
VS Code is able to find the place to stop in source code
Actual:
Stopped at a place and show:
Source /home/tester/Documents/test345217270346263225/a.cpp is not available.
Investigation:
There is no such path /home/tester/Documents/test345217270346263225/,
it should be /home/tester/Documents/test司法
Inside of MI mode, GDB sends the actual document using Unicode escapes. For instance in the case I am looking at, the actual returned path is /home/jacdavis/tests\345\217\260\345\214\227/a.out.
That is a gdb bug. We should check and see if we can work around this by translating those back to Unicode, but we may be out of luck here.
The text was updated successfully, but these errors were encountered:
Internal bug id: 196744
Repro:
Puting your source code under path like: /home/tester/Documents/test司法
Open in VS Code
Set some BP
F5 tostart debugging
Expected:
VS Code is able to find the place to stop in source code
Actual:
Stopped at a place and show:
Source /home/tester/Documents/test345217270346263225/a.cpp is not available.
Investigation:
There is no such path /home/tester/Documents/test345217270346263225/,
it should be /home/tester/Documents/test司法
Inside of MI mode, GDB sends the actual document using Unicode escapes. For instance in the case I am looking at, the actual returned path is /home/jacdavis/tests\345\217\260\345\214\227/a.out.
That is a gdb bug. We should check and see if we can work around this by translating those back to Unicode, but we may be out of luck here.
The text was updated successfully, but these errors were encountered: