Debugger crash in V1.8.4, V1.8.5 and V1.8.6 on Linux - V1.8.2 works - Example code inside. about vscode-amiga-assembly HOT 8 CLOSED

Regarding executable flag, uae-dap tries to fix this and chmod the binary before executing it. Obviously it's not working in this case. Perhaps it doesn't have permission to do so in Linux. I'll look into this.

from vscode-amiga-assembly.

@prb28 Ok, great, thanks, missed that.

from vscode-amiga-assembly.

@grahambates can you look at this please ?

from vscode-amiga-assembly.

I managed to debug on ubuntu 22.04 even if I had the same issue.
Please try:

• chmod u+x /home/user/.vscode/extensions/prb28.amiga-assembly-1.8.7/dist/bin/fs-uae/fs-uae-linux_x64
• Modify your ~/.bashrc
  export LD_LIBRARY_PATH=/home/user/.vscode/extensions/prb28.amiga-assembly-1.8.7/dist/bin/fs-uae
• uncheck the "All Exceptions" in the breakpoints view
  
• Start debuging with fs-uae
  I'll try with a debian 12 vm when it will be ready.

from vscode-amiga-assembly.

The workaround is efficient on debian 12 too.

from vscode-amiga-assembly.

@prb28 I can confirm from a quick test that unchecking "All Exceptions" has fixed the issue and I can debug. Awesome.

from vscode-amiga-assembly.

@prb28

I tested this again using V1.8.7 pre-release version.

The chmod was not necessary, +x was already set.

I then tested with the LD_LIBRARY_PATH set as well as without it and with libsdl2-ttf-2.0-0 installed instead (in order to not get the "[EMU] No suitable emulator binary" error).

I also tested with and without "All exceptions" set.

In all cases what happens is the following:

The debugger stops on the second instruction movem.l (sp)+,d0-a6, even if there's no breakpoint set, but it doesn't crash as before or land at some other unrelated instruction as originally. So continuing will either finish or stop at the next actually set breakpoint, debugging seems to work except for that stop at the second instruction.

If I comment out movem.l (sp)+,d0-a6, it stops at clr d0, so again, it's the second instruction.

A breakpoint at the first instruction is ignored, it still stops at the second instruction.

A breakpoint at the second instruction, doesn't change anything.

Only with "All execeptions" set it now crashes after the code finishes at: 0x00fc08e6: ori.w #$2000, sr, where it crashed before as described in the original post.

So disregarding the unprompted stop at the second instruction and a breakpoint not working at the first instruction, with "All exceptions" unset, debugging seems to work.

from vscode-amiga-assembly.

@Jasmin68k In the default launch configuration the "stopOnEntry": true, option is set. This makes the program stop at the second instruction. There is no way to stop it at the first instruction.
If you set this option to false, it will continue until your first breakpoint.

from vscode-amiga-assembly.