search

prb28 / vscode-amiga-assembly

Amiga Assembly extension for Visual Studio Code
GNU General Public License v3.0
179 stars 12 forks source link

Debugger not activating #205

Closed Bippym closed 2 years ago

Bippym commented 2 years ago

I am including files and find the debugger isn't activating when a breakpoint is placed in any included file except my main.asm (which is included itself).

See the following video https://youtu.be/e5w0bJveOvU

prb28 commented 2 years ago

You have a build error in you main file. I think the new binary is not linked so you are debugging the old program. Try to delete the executable file and build again. I think you would not have a new file created.

Bippym commented 2 years ago

I already had deleted them. The errors are shown below, and if I compile again immediately the errors clear.. Go figure

I also don't know why I get random relocation errors

image

prb28 commented 2 years ago

There are two sources for errors : vasm and vlink. When you edit vasm the extension only runs a vasm compilation on the file and shows the errors -> no error in your case. When you run your program the extension compiles the files with vasm and link them with vlink. You can have vlink errors during this build. these are the errors you are seeing in you screen shot. If vlink has error, you will not have a new executable.

Bippym commented 2 years ago

I am getting a new executable. I deleted everything from the build folder and my main exe from dh0.

Let me know if you need my source, and a place to send it. I don't necessarily want it made public. It is Diiiirty

prb28 commented 2 years ago

Yes, if you can send me the sources that will help. I've tried modifying the example and adding sources and it worked. You can send me it by pm on eab, discord or mail.

Bippym commented 2 years ago

What's your discord name? Are you in any of the Amiga den groups?

prb28 commented 2 years ago

I'm on the amigadev group.

prb28 commented 2 years ago

Got you source thanks. There is something wrong with the segment resolution. If you want to debug you code (before I manage to find and fix this bug). You have to add a breakpoint in the main source file "Main.asm". As a example in front of the line:

bsr        BLIT_PIPE_I

When the program hit the breakpoint. Do a "step into" command (F11) and you get into the source. When the source is stepped like that you can add breakpoints normally in this file. When you stop and restart these breakpoints are broken, you'll have to do the same process.

prb28 commented 2 years ago

Fixed in 1.3.1 pre-release.