Asm-One Debugger
 

I find that the Asm-One Assembler seems to function fairly intuitively although I like the convenience of Vasm better, I still need a debugger for either.

I start Asm-One, r)ead a simple source code file, a)ssemble it, pass1, pass2, no errors, right mouse menu Debugger and the screen clears… F12 still works for WinUAE but otherwise just gray screen. The Asm-One use manual treats Debugging like “no big deal” but I can’t get it to open, tried “d” from the assembler command line, but that looks like a memory dump.

What have I goofed up this time?

Any recommendation on other Debuggers?

D is the command for D.isassembling, it is not the debugger.
To open the debugger right after assembling, use AD (A.ssemble D.ebug).

Thanks for the reply StingRay, AD goes to the same gray screen, I have to F12 back to WinUAE, then Quit or Reset to get back to Amiga.

Which ASM-One version are you using? Older versions have problems with 040/60 CPUs.

V1.48, should I try an A1200 WinUAE configuration?

V1.48 works fine for me, debugger runs without problem. What is your WinUAE config?

Standard A4000 with exception of full screen window.

Is JIT enabled? If so it needs to be turned off.

The only JIT I found is in the CPU/FPU tab, and it's not checked.

Thanks for the replies StringRay, it’s clear to me that if a 14 year member with 6000 posts doesn’t see an immediate solution, I’ve got something seriously screwed up somewhere. I’ll save my Amiga PC directory, then return my VirtualBox XP system back to the way it was before WinUAE, then reload WinUAE, & Asm-One.

I have tried several WinUAE configurations but ASM-One's debugger worked fine with all of them so I am unfortunately unable to reproduce your problem. What might make a difference is the stack setting, try increasing it before starting ASM-One. Another thing you could try is using a different ASM-One incarnation, i.e. ASM-Pro. Maybe that one works better on your system.

For a debugger where the system is running I am a great fan of BDebug from the Barfly package. (And I use BAsm too.)

BDebug is nice, I am using DBug from the OMA package for system-friendly stuff though and can highly recommend it.

Try V1.29 or V1.49 rc2.

Well, I went back to a copy of the VirtualBox before I originally loaded WinUAE, redid the install tutorial, and reloaded Asm-One, all good practice (I learn best by doing, and both Amiga and WinUAE are making more sense). Asm-One debugger is barfing in the same place, although different chunks, I know this has to be my configuration, so I guess I’ll try a different version of Asm-One, then barfly. I don’t know what Sting-Ray’s reference to “the OMA package” was, but if someone can link me to a download of that, I’ll try it too.

OMA is an Assembler package ("O.ptimising M.acro A.ssembler") which contains the DBug debugger. Wepl has recently uploaded V3 to the Zone here on EAB where you can download it. I have never really used the assembler but the debugger is excellent for system-friendly stuff.

I've been having this same grey-screen problem with Asm-One*. I first noticed it some years back and figured there was something wrong with my UAE conifg** so if you ever figure it out please post the solution.

In the mean time the debugger in both AsmPro 1.18 and Photon's AsmTwo 0.96w2 work fine for me.

* - Asm-One versions 1.48 and 1.49-RC2.

** - A1200 config with Kickstart 3.1 and 4MB Fast RAM.

I'll keep you in mind should I find a fix for the issue, what version of Windows and WinUAE you on? I'm on XP and 4.2.1.
Thanks for the software pointers.

I'm using Windows 10 with WinUAE 4.3.0.

FYI I have the exact same issues in FS-UAE under Mac OS X running a similar config.

That, then smells like Asm-One to me. Of AsmPro 1.18 and Photon's AsmTwo 0.96w2 which one do you like?