Amiga Assembly extension for Visual Studio Code

[roondar]

I've recently become re-aware of this and tried it out. It seems to work well enough, but I can't get the WinUAE debug (or run) to work. Only FS-UAE seems to work, the WinUAE configurations give the error "unknown type: WinUAE".

Does anyone know how I can fix this?
Because source level debugging my HW banging asm code is such a nice feature I really would like to have it working, preferably in WinUAE

[BippyM]

Originally Posted by roondar

I've recently become re-aware of this and tried it out. It seems to work well enough, but I can't get the WinUAE debug (or run) to work. Only FS-UAE seems to work, the WinUAE configurations give the error "unknown type: WinUAE".

Does anyone know how I can fix this?
Because source level debugging my HW banging asm code is such a nice feature I really would like to have it working, preferably in WinUAE

Same for me.

[prb28]

Originally Posted by emiespo

Hi, let me say that the Amiga Assembly extension for VSC is really great, and express my gratitude.

Thanks !

Originally Posted by emiespo

Following up on this example I have a question: is it possible to launch the debugger as if the exec were launched via CLI? While debugging I can't open a library that is not in ROM (asyncio), and that is stopping me from being able to properly debug.

If you dynamically load your library, you must try with an absolute path.
I don't really know all the surroundings of the CLI. One I've tried to rework the exe load sequence but didn't succeed to have something better.

You should try the winuae version, I think it's more CLI compatible. A merge with fs-uae is possible, but, that's some work...

[prb28]

Originally Posted by roondar

Does anyone know how I can fix this?

Try from a clean example project download : https://github.com/prb28/vscode-amig...indows_x64.zip
It should work.

[roondar]

Originally Posted by prb28

Try from a clean example project download : https://github.com/prb28/vscode-amig...indows_x64.zip
It should work.

Ok, that does work.
Strange... I only first downloaded and installed the extension/example two days ago and it most definitely didn't work at the time. At any rate, it works now so thanks for the help. I'll be trying this out for sure

Edit: it is possible the link via the marketplace doesn't work and the one you gave does? Because I installed it through the VS Code marketplace and your link is directly from Github.

[prb28]

Originally Posted by roondar

it is possible the link via the marketplace doesn't work and the one you gave does? Because I installed it through the VS Code marketplace and your link is directly from Github.

Which link did you use ? this : https://github.com/prb28/vscode-amig...ample/releases ?

[roondar]

Originally Posted by prb28

Which link did you use ? this : https://github.com/prb28/vscode-amig...ample/releases ?

Yes, that's the one. And then I picked https://github.com/prb28/vscode-amig...indows_x64.zip

Not quite sure what went wrong then, because that does seem to be the exact same link as you sent me. At any rate, it works now and I'm quite impressed with how easy it all works so far. I love the way the registers show the meaning of their bit values when you hover over them. Saves me looking them up!

Granted, I've yet to try many things but that's half the fun

[prb28]

Yes, it's the same link and I did not update it recently.

To start discovering the extension, you have some features in the wiki : https://github.com/prb28/vscode-amiga-assembly/wiki

If you want to try some useful (not so clearly explained) options :

• drag your mouse hover a variable and it will be evaluated
• add a watch value with the memory dump syntax : https://github.com/prb28/vscode-amig...ugger-commands

[BippyM]

How exactly does one use the debugger commands? Like where are these entered and set?

How do I view the memory pointed to by an address register?

[prb28]

Originally Posted by BippyM

How exactly does one use the debugger commands? Like where are these entered and set?

How do I view the memory pointed to by an address register?

In the lower part (input field) of the "Debug Console" type "m 5c50,10,2,4" to print the contents of $5c50.


You can add a watch an type the same command.


Screen example :

https://github.com/prb28/vscode-amig...the-watch-view

[BippyM]

I have followed this, and it displays from mem location 0 or doesn't show from the memory location I set.


I have tried with both FSUae and Winuae

Originally Posted by prb28

In the lower part (input field) of the "Debug Console" type "m 5c50,10,2,4" to print the contents of $5c50.


You can add a watch an type the same command.


Screen example :

https://github.com/prb28/vscode-amig...the-watch-view

[prb28]

Originally Posted by BippyM

I have followed this, and it displays from mem location 0 or doesn't show from the memory location I set.

I think, I've something wrong in my documentation, try with the address :

"m $184b2,10,2,4"

[BippyM]

Spot on, that has fixed it. Thank you

Would it be possible to have the ability to right click on a register/label and select for it to display the memory location?

[prb28]

Originally Posted by BippyM

Would it be possible to have the ability to right click on a register/label and select for it to display the memory location?

Yes, I've added a feature request (https://github.com/prb28/vscode-amig...bly/issues/140) in the github project, feel free to add more.

[emiespo]

Originally Posted by prb28

Thanks !







If you dynamically load your library, you must try with an absolute path.

I don't really know all the surroundings of the CLI. One I've tried to rework the exe load sequence but didn't succeed to have something better.



You should try the winuae version, I think it's more CLI compatible. A merge with fs-uae is possible, but, that's some work...

Thanks for your reply!

I tried with every possible path, absolute, relative, etc... I believe the issue is in the way the emulator is called. In the run config, you can see the emulator will just start off the disk and follow the normal startup-sequence, in debug mode, the exec is just “passed” to the emu.



Unfortunately I can’t use a Windows machine atm. I’ll give it a go when possible, just to see if the same issue happens.



On a different topic, still related to the fs-uae debugger, is there a way to debug a memory location with a labelled offset from a register? I can’t find a way...



Ie:



move.w d0,myLabel(a0)



...it won’t find the symbol “myLabel”. It only seems to work with absolute addresses. Either I don’t know how to do it, or is this an actual limitation of fs-uae?

[prb28]

Originally Posted by emiespo

move.w d0,myLabel(a0)

...it won’t find the symbol “myLabel”. It only seems to work with absolute addresses. Either I don’t know how to do it, or is this an actual limitation of fs-uae?

This is part of the extension syntax parse. I didn't add this case.
You can try :
m ${mylabel}+${a0},10,2,4
or m #{mylabel}+${a0},10,2,4 (I think I've a bug on this)

[BippyM]

Any idea why my registers are no longer showing?

[prb28]

Originally Posted by BippyM

Any idea why my registers are no longer showing?

No idea. The debugger didn't retrieve fs-uae debug info.
Try :
- set a breakpoint at the beginning of the program (3rd line) or set stop at entry in the launch params : "stopOnEntry":true
- Run with winua
- Clean the workspace and the unwanted .s files
- modify the launch command to add "trace":true - you should see the communications between fs-uae and vscode

Otherwise : I can have a look if you send me the folder.

[BippyM]

Find my (your) workspace attached. I haven't included the bin folder which is unmodified.


Ignore my spaghettiness (unless it is the reason the debugger isn't working at all). No breakpoints are working


I haven't done anything since last night apart from start to split my code across multiple files (poorly I may add)


Thjanks

Originally Posted by prb28

No idea. The debugger didn't retrieve fs-uae debug info.
Try :
- set a breakpoint at the beginning of the program (3rd line) or set stop at entry in the launch params : "stopOnEntry":true
- Run with winua
- Clean the workspace and the unwanted .s files
- modify the launch command to add "trace":true - you should see the communications between fs-uae and vscode

Otherwise : I can have a look if you send me the folder.

[prb28]

Originally Posted by BippyM

Find my (your) workspace attached. I haven't included the bin folder which is unmodified.

Thanks for the workspace.
Well, I saw it... start to debug trying to understand, and it started working and I can't make it fail again !

What I did before it works :
- I've edited the launch file and removed all the configurations, kept only one debug configuration and start debugging (F5).
I thought it was a corrupted file but restoring the zip does not make it fail again.

Can you try the same procedure ?
Does it work with default workspace ?
(This is the 'science' part of 'computer science' )