Unable to establish a connection to GDB!

[Cryosignal]

Howdy! I'm following along with the videos and readme file. I've gotten to the point in the video where we run the debugger and it opens up mGBA to see all the pretty colors displayed. But I'm receiving the same error message as user Aljenci posted in another thread. Though in my case mGBA never opens and I'm greeted with these errors.

Then...

This also gets printed in the debug console

I also noticed in the terminal I was receiving an error.

After adding a GBA folder to my desktop it changed to this

I tried adding the devkitpro\tools\bin addition to the path but that didn't seem to change anything.

Any advice on this problem I'm thankful for. It seems like I really goofed something up along the way to be getting this many errors...

[JamieDStewart]

Hey there, looks like you might have a space in your working directory path. Looks like you have your GBA code in a folder in your one drive that is called something like "GBA: "... I dont' know the rest as that's where the error cuts off when it finds the first space, there is probably a way around this using quotation marks and some further directory substitution with environment variables but it is honestly just far easier to have your work in a directory with no spaces "GBA_Dev" etc.
So change your project directory name and see if that fixes it up.

[Cryosignal]

Ah I did indeed have a space in my folder name! Though after removing the space I still receive the same error eveywhere except the terminal.

The error says "arm-none-eabi-gcc" doesn't exists! I assume it means the arm-none-eabi-gcc.exe? If it is then its in the devkitARM bin folder.
I'm going to try setting this up on a different computer just to give it another try.
Thank you for the speedy response!
.

[JamieDStewart]

Hi Can you confirm that you have devkitARM installed as part of devkitpro and that you have the arm-none-eabi-gcc.exe executable contained in the devkitPro/devkitARM/bin/ folder.

[janplaehn]

Hey there! I've got the exact same error and I can confirm that I have devkitARM as well as the arm-none-ggc.exe executable in the right places. For me, mGBA also launches before the "Unable to start debugging. Unable to establish a connection to GDB" appears

[janplaehn]

My Debug Console:

Starting: "C:/devkitPro/devkitARM/bin/arm-none-eabi-gdb.exe" --interpreter=mi
"C:/devkitPro/devkitARM/bin/arm-none-eabi-gdb.exe" exited with code -1073741515 (0xC0000135).

My output:

Error: the description can't be converted into a problem matcher:
{
    "background": {
        "activeOnStart": true,
        "beginsPattern": "^.*debuggerReady.*$",
        "endsPattern": "^.*debuggerReady.*$"
    }
}

Error: the description can't be converted into a problem matcher:
{
    "background": {
        "activeOnStart": true,
        "beginsPattern": "^.*debuggerReady.*$",
        "endsPattern": "^.*debuggerReady.*$"
    }
}

[janplaehn]

Upon further inspection I did figure out both a .gba and a .elf file get generated in the project folder and opening them manually with mGBA works just fine! However, this way there is no debugging functionality at all.

[Fast4WD]

Has anyone found a solution to this problem yet?

[Fast4WD]

Guys, I think I might have found a solution, but I'm not completely sure.

What I did was just copy the "libgcc_s_seh-1.dll" and "libstdc++-6.dll" from the C:\devkitPro\tools\bin folder to the C:\devkitPro\devkitARM\bin folder.

If you have a problem with the localhost line just remember to not close mGBA (or whatever emulator you're using)

/I'm sorry if my English is bad

[joeylmartin]

I'm having the same output as janplaehn, but Fast4WD's solution isn't working for me.

[rawbits2010]

I had a similar problem using mGBA 0.10.1 - the readme said it might not work. The cause is the terminal hangs after executing the command (aka launch mGBA) and gdb never tries to connect. This can be confirmed by the echo not being executed until mGBA is closed (+ sleep 5 ofc).

So I started mGBA using "start" which will not hang the terminal and it works. I also got rid of the shady "debuggerReady" business cause it didn't make sense to me as the debugger has the option to wait for a connection that defaults to 10000 ms.

		{
			"label": "gdb-debug",
			"type": "shell",
			"presentation": {
				"echo": true,
				"reveal": "always",
				"focus": false,
				"panel": "shared",
				"showReuseMessage": true,
				"clear": false
			},
			"dependsOn": [
				"make debug"
			],
			"isBackground": false,
			"windows": {
				"command": "start C:/mGBA-0.10.1-win64/mGBA.exe -g ${command:extension.commandvariable.workspace.folderPosix}/${workspaceFolderBasename}.gba"
			}
		},

The "presentation" part shouldn't matter and I needed an extension to get the workspace path with forward slashes 'cause mGBA complained.

Hope this helps. Cheers!