GDB launch issue. Could not deternine path to index cache directory.

[dvescovi1]

I am using VS Code on Windows 10.
I have installed the GNU ARM tool chain 8.2.1 and GNU debugger.
I also have JLINK 644e installed.
I had this setup working before on another W10 setup but on my new setup I am getting this error on launch:
"C:\Program Files (x86)\GNU Tools ARM Embedded\8 2018-q4-major\bin\arm-none-eabi-gdb.exe: warning: Couldn't determine a path for the index cache directory."

Here is my launch.json:

{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"type": "gnu-debugger",
"request": "launch",
"name": "GNU debugger",
"program": "${workspaceFolder}/build/wasp_M4.elf",
// "toolchain": "${config:arm-none-eabi.bin}",
"client": "arm-none-eabi-gdb",
"server": "JLinkGDBServer",
"windows": {
"server": "C:/Program Files (x86)/SEGGER/JLink_V644e/JLinkGDBServerCL.exe",
},
"serverArgs": [
"-device", "MIMX8MM6_M4",
"-if", "SWD",
"-speed", "4000"
],
"serverPort": 2331,
"customVariables": [
"port0",
"port1",
"port2",
],
"autoRun": false,
"debugOutput": false,
}
]
}

Any ideas what might be the issue?

[dvescovi1]

This seems to be an issue only with GNU ARM tool chain 8.2.1 (to date the latest release).
I reloaded 7 2018-q2-update and it works fine.

[beYunfei]

hi,

I met the same issue as this,actually this warning stops launching my debug session.

May I ask is there a way to figure how the gdb client is started with what parameters?
Why I am asking is because I can run my gdb fine with my script in cygwin like:
arm-none-eabi-gdb --init-command "my_jlink_gdb.script"

my vs code configuration is like:

            "client": "arm-none-eabi-gdb.exe",
            "server": "JLinkGDBServerCL",
            "clientArgs": [
                "--init-command", "out/sandbox_jgdb.jlink",
            ],
            "serverArgs": [
                "-device", "cortex-m3",
                "-if", "SWD",
                "-speed", "4000",
                "-port", "2331"
                ],

[schroeca]

could you please share your latest configuration, that is working?
I am using vscode: 1.44

[beYunfei]

@schroeca I was not able to figure out how to use "--init-command" within "clientArgs", did you make it work?

My work-round was wrapping the whole command in a script within "serverpath" like
"serverpath": "${workspaceRoot}/tools/vscode-launcher/customized-jlink-launcher.sh",

in my "customzied-jlink-launcher.sh"
I put some code like:
JLinkGDBServerCL.exe -singlerun -halt -strict timeout 0 $@

hope it helps

[beYunfei]

BTW, I am using the latest vscode. 1.44.1

[tdjastrzebski]

I have the same issue with GNU ARM version 9 2019-q4-major.
I found this warning comes from dwarf-index-cache.c file but did not find how to get rid of it.

[hwmaier]

Just a note: setting the XDG_CACHE_HOME environment variable to something like c:\User\myname.cache worked for me.

[spg-one]

Add a system environment variables named HOME like this⬇️

then restart your PC