-
Notifications
You must be signed in to change notification settings - Fork 240
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
Issue handling paths with non-ascii characters on Windows (?) #207
Comments
I think this a problem with gdb itself. I think you will run into other problems over time with non-ascii chars in path names. Does your basic debug session still work? If so, there can be a workaround. |
Thanks for the quick comment! On my setup GDB works from the path Given that, I could it be that sourcing the gdbsupport.init on this line Line 308 in afab539
is not platform independent on handling the path - not escaping non-ascii? I agree that non-ascii in paths is calling for trouble, but I'm just looking to help a colleague who happens to have a non-ascii in his username. |
I am not even sure how to escape Unicode chars for gdb machine interface which is plain text. It is not like HTML or C strings where you can do \uXXXX. The code you pointed out uses microsoft/vscode-cpptools#1998 See if you can manually start gdb command line and find a way to source that file. The only way I know how to handle Unicode paths on Windows for tools like gdb is to convert all pathnames to 8.3 DOS format but that is not a good solution. |
Thanks, I created a symlink with non-ascii to start gdb as follows: Tested with:
|
But you are right, sourcing the same file does not work as gdb converts
|
If cortex extension would support configuring the path of |
Btw, with gdb, always use forward slashes. That file is only the beginning of issues. You will see many more. Also, the extension does not decide where the info lives. VSCode does and it affects every extension. VSCode does offer a command-line option to specify extension-dir... You can launch VSCode like.
My suggestion is to change the User's folder-name. It is bit complicated but in the long run, it is best. You can avoid the "death by a thousand cuts" problem :-) Anything compiled with mingw or cygwin or even Windows programs are known to fail. |
Help from
|
Thanks @haneefdm |
Extension works great with GDB on my setup.
I encouraged a colleagues to use it as well.
Setups are identical except for a non-ascii character in his Windows 10 UserAccount and starting the debugger results in:
"c:/Users/AColleagueWith_An_ä_In_His_Name/.vscode/extensions/marus25.cortex-debug-0.3.1/support/gdbsupport.init: No such file or directory."
The text was updated successfully, but these errors were encountered: