Pre-release vscode amiga assembly with WinUAE integration

[prb28]

Originally Posted by JoeJoe

Unfortunately I cannot confirm this. The debugger unfortunately does not stop. Tested with 0.20 version (mac+win)

You must have the 0.21 extension, it's a new parameter.

[JoeJoe]

So when I run the code, the debugger stays here. Not what you expect.

[prb28]

[QUOTE=defor;1441673
So far I've encountered only one minor issue: When I place a breakpoint, the executable stops but at a different location (yet inside my code).[/QUOTE]
Please try this winuae.exe build : https://github.com/prb28/vscode-amig...re3/winuae.exe
It should be fixed.

[prb28]

Originally Posted by JoeJoe

So when I run the code, the debugger stays here. Not what you expect.

Need to debug...

[Antiriad_UK]

Originally Posted by prb28

Please try this winuae.exe build : https://github.com/prb28/vscode-amig...re3/winuae.exe
It should be fixed.

Yes, looks good So a bug in the Winuae changes?

[prb28]

Originally Posted by Antiriad_UK

So a bug in the Winuae changes?

Yes...
Adding a breakpoint generated an event treated as a breakpoint hit in the gdbserver additions. Some flag / global variable was triggering that. I think my last merge with the main branch of bartman did it.
My code needs some review by tonioni...
I should take some hours to have a better comprehension of winuae/fsuae, but it's huge and complex ! So I learn things with bugs, or "oops", this doesn't do what I thought...This extension is challenging in every point (I am a noob in each one) :

• vscode and the plugin mechanism / typescript
• amiga knowledge
• 68k assembly
• UAE - WinUAE and FS-UAE
• building the code on different platforms
• github and all the building / testing servers
• gdb remote protocol

When I stated it it was just because I wanted to format my asm code !
And my stupid coder mechanism, each time I tell to myself : it would be cool to have.... and there we go...

[Antiriad_UK]

Originally Posted by prb28

Yes...
When I stated it it was just because I wanted to format my asm code !
And my stupid coder mechanism, each time I tell to myself : it would be cool to have.... and there we go...

It's good for us

[defor]

Originally Posted by prb28

Please try this winuae.exe build : https://github.com/prb28/vscode-amig...re3/winuae.exe
It should be fixed.

I also confirm that it is fixed. Thank you!
P.S.: VSCode with your addon is currently the best assembler IDE for (classic) Amiga. Ever.

[prb28]

Thanks !

[JoeJoe]

I have a strange behaviour when I start the debugger. As soon as I press F5 in VS code WinUAE starts with 250 FPS. This looks like this:



I cant debug anything. But when I press Shift+F12 in WinUAE, WinUAE is connected to VS Code and I can debug normally. Here is the log after the action:



These are my options:

"-s",
"debugging_features=gdbserver",
"-s",
"debugging_trigger=SYS:amiga",
"-s",
"filesystem=rw,dh0:${workspaceFolder}\\fs-uae\\hd0\\",

[Antiriad_UK]

The modified winuae.exe runs in warp mode right up until the "debugging_trigger" exe loads then it should drop back to normal speed. Check that SYS:amiga is exactly right.

[JoeJoe]

Many thanks for the hint. When I remove the SYS, it runs wonderfully, like this.

"debugging_trigger=amiga"