WARNING: The examine memory location command won't work

[boyedarat]

What do these warnings mean?
Code-Debug WARNING: Utility Command Server: Error in command socket Error: listen EACCES C:\Users\st4r\AppData\Local\Temp\code-debug-sockets\Debug-Instance-n8sl
Code-Debug WARNING: The examine memory location command won't work

I get this warning when debugging a Rust program using GDB. Is this related to this enhancement?:
#64

[WebFreak001]

well these warnings mean that "The examine memory location command won't work"

Otherwise you can just ignore them. I should fix this on windows

[Lin-H]

I have the same problem with Rust debugging. It's not just warning.
An error occur Debug adapter process has terminated unexpectedly
So it couldn't work

VSCode 1.6.1
GDB 7.12
Rust 1.12.1

[WebFreak001]

no it most likely doesn't have anything to do with that crash, try checking out #59. Otherwise does it print anything to the console before crashing other than that warning?

[Lin-H]

I figured it out ! First I just put gdb.exe in the PATH, I can use it in the command line, but maybe it's not enough. So I put the whole folder E:\msys64\mingw64\bin in the PATH.
IT WORDED !
Thank you for your help @WebFreak001 . I thought the plugin crushed at first.

[ctaggart]

I also get the error when trying to debug and I can't seem to hit a breakpoint.

Code-Debug WARNING: Utility Command Server: Error in command socket Error: listen EACCES C:\Users\cameron\AppData\Local\Temp\code-debug-sockets\Debug-Instance-mjhs
Code-Debug WARNING: The examine memory location command won't workNo symbol table is loaded.  Use the "file" command.
No symbol table is loaded.  Use the "file" command.

Latest installed:

PS C:\Users\cameron\rs\app1> cmd /c where gdb
C:\msys64\mingw64\bin\gdb.exe
PS C:\Users\cameron\rs\app1> gdb --version
GNU gdb (GDB) 7.12
PS C:\Users\cameron\rs\app1> rustc --version
rustc 1.12.1 (d4f39402a 2016-10-19)
PS C:\Users\cameron\rs\app1> code --version
1.7.1
02611b40b24c9df2726ad8b33f5ef5f67ac30b44

[ctaggart]

Ugh, for me it looks like the important error is:

No symbol table is loaded.  Use the "file" command.

And this is probably because I'm using the wrong toolchain:

PS C:\Users\cameron\rs\app1> cmd /c where rustc
C:\Program Files\Rust stable MSVC 1.12\bin\rustc.exe

I'll get some sleep and fix that. Sorry to bother.

[tokenclt]

I have the same problem with Rust debugging on windows. I also found that when I hovered my cursor on a variable with complex type (for example a string Iterator ) , the debugger would crash. While the primitive types would show there content correctly.

VS Code: 1.7.1
Rust: GNU 1.12
GDB: 7.9.1

[GitMensch]

Other than the complete move for the memory location it may be possible to use https://code.visualstudio.com/api/extension-guides/virtual-documents instead of sockets or file api and use that (maybe only possible if it is opened in the hex-editor).