ASM: Asm-ONE or AsmPro - how to set a Hello amiga coders, I hope it is ok to hijack ?

[Fireball]

Hello amiga coders,

I have tried to set a breakpoint in my code (left amiga button + b) but it does not work. When I type "ad" the program stops always at the beginning of my program. When I press (left amiga button + r) in debug mode the debuger does not stop at my breakpoint aswell he jumps directly to my rts command.


Best regards

fb

[StingRay]

Does your program kill the system (i.e. disables interrupts/DMA)?

[Fireball]

Hello StringRay,

first of all I have to apologise my headline is broken. I mean "ASM: Asm-ONE or AsmPro - how to set a breakpoint ?"

My program doesn't kill the system. I would like to set a breakpoint and then go through my program step by step to get some informations about variables i.e. test : dc.w 1,2,3 or registers. I don't want to start every time in line 1.

Best regards

Fb :-)

[Photon]

Late reply, but this is one of the reasons I updated the debugger in AsmTwo.

As Stingray says, if you turn off (too many) interrupts, you will disable the OS that the debugger uses for key presses etc.

After that it's about the handover back to the Assembler window to function properly. On some KS/WB versions you may see a blank screen with the WB colors. In this case, move your mouse (blindly) to the top of the screen and click and drag down. The previous screen appears. This trick may work also with some Asm-One and AsmPro versions.

With AsmTwo, you can always debug your in-game or in-demo code, even with most (but not all) interrupts turned off.

[admiral]

Originally Posted by Photon

With AsmTwo, you can always debug your in-game or in-demo code, even with most (but not all) interrupts turned off.

Love AsmTwo, looking forward to seeing a new version (been a while).

How does this work behind the scenes? On breakpoint you set system-friendly vectors and reenable? Is there more to this?

[a/b]

Once you are in debugger (AD command or amiga-shift-d), press amiga-b and then select a line where you want a breakpoint, or press amiga-shift-b to enter a breakpoint address.
These breakpoints use the illegal instruction vector (they replace opcodes with illegal to trigger an exception) and don't rely on interrupts or OS being active.

If you use asm-pro v1.19 or newer, you can also use the ADDBP directive in your source code to set breakpoints that will be auto-activated once you start debugging. From the "release notes":

2. ADDBP directive to add a breakpoint from the source code
Syntax is:
	ADDBP	<expression>
For example:
	ADDBP	Label1234
	ADDBP	$30000+idx*4
Assemble your code with AD and unconditional breakpoints will be activated and ready to go.

[Photon]

Originally Posted by admiral

Love AsmTwo, looking forward to seeing a new version (been a while).

How does this work behind the scenes? On breakpoint you set system-friendly vectors and reenable? Is there more to this?

<3

Lots of painstaking debugging-the-debugger on all my Amigas for handling stack and switch to/from Supervisor, VBR fix, and more recently comments and blank lines in macros causing a vertical offset of the marked line.

[admiral]

Originally Posted by Photon

<3

Lots of painstaking debugging-the-debugger on all my Amigas for handling stack and switch to/from Supervisor, VBR fix, and more recently comments and blank lines in macros causing a vertical offset of the marked line.

Thank you a lot for the toil.

Nothing is ever easy, but it is all worth it at the end.

[malko]

Originally Posted by admiral

Love AsmTwo, looking forward to seeing a new version (been a while). [...]

+1.
Hope Photon found it relevant enough also to have a look at the shortcuts that do not follow the key mapping you are using but are instead bound to key position on the keyboard. For non "us" keyboard this is really annoying: https://eab.abime.net/showpost.php?p...09&postcount=3