Comments (10)
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
from gba_vscode_basic.
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.
from gba_vscode_basic.
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!
.
from gba_vscode_basic.
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.
from gba_vscode_basic.
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
from gba_vscode_basic.
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.*$"
}
}
from gba_vscode_basic.
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.
from gba_vscode_basic.
Has anyone found a solution to this problem yet?
from gba_vscode_basic.
I'm having the same output as janplaehn, but Fast4WD's solution isn't working for me.
from gba_vscode_basic.
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!
from gba_vscode_basic.
Related Issues (8)
- Mac: GDB Timed Out!
- White screen HOT 4
- mGBA 6.2 not working in macOS Mojave (10.14.6) HOT 1
- Debug woes on macOS, can't start a debugger HOT 5
- mGBA debugging not working HOT 7
- Couldn't find a debug adapter descriptor for debug type 'cppdbg' (extension might have failed to activate) HOT 1
- Linux setup? HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gba_vscode_basic.