Amiga.org
Operating System Specific Discussions => Amiga OS => Amiga OS -- Development => Topic started by: gazsp on October 31, 2005, 11:09:08 PM
-
Does anybody know of any tools available (on Aminet for example) that would aid debugging and development on OS3?
I'm currently using Cygwin with GCC cross compiled for m68k-amigaos to produce the code, and WinUAE and an A1200 to test the code.
-
Well, they aren't debugging tools that operate at source level or anything, but enforcer (or the Mu tools equivalent) is very handy for spotting all manner of illegal pointer accesses and Mungwall is handy for finding pesky out of bounds access in memory allocations.
Between them they cover the majority of common mistakes I would say.
-
SASC's source level debbuger is beautifull. But it doesn't seem to accept input from other compilers. A while ago I compiled a few times with VBCC and if a nasty bug appeared I'd use SASC and it's debugger. But I can't do that anymore cause my code now needs the long long type (covered by ISO99 or something) wich SASC can't handle).
Other than that GDB (if that's the name of it), the one that's normally used with GCC should work no ? It's a pain to use, command line only. I haven't tried it though, cause I use VBCC for all my compiling and I don't want to switch, VBCC rules, just wish they made a cool debugger for it.
Oh, I normally use Printf() ...(hides... :lol:)
-
Well printing out values at the place you first suspect a problem is generally OK, but in a complex bit of code it might not be possible (ie some hardware lock or perhaps in a Task or something).