I am trying to debug a tricky crash that only happens on OS4 using both m68k and PPC builds of my app (the m68k version runs fine on OS3) but I'm having a hard time debugging it.
It's crashing in a call to IDOS->Read() and I don't know why, and when I look at the call stack in Grim Reaper, I get this:
after a few years, I come back again to the Amiga dev. I have again some spare times :-)
I'm looking for a debugger which can execute asm code step by step.
I tried Debug 101, several GDB (Latest SDK, OS4Depot). None permit the single step.
GDB stop only at first breakpoint and no more at others.
Is there any GDB version or other debugger available for Amiga OS 4.1.
I still have the 'pre-release' version. The one I got when buying the X5000.
Lately, I am experimenting with a 68k application, trying to compile it for OS4. It uses vbcc to compile, so I am using the same and for now, I am not thinking to switch to GCC.
I managed to compile the application, but unfortunately, it crashes at some point and I thought to use crashlogs to figure out where exactly that happens. I found the awesome guide by Hans at https://hdrlab.org.nz/articles/amiga-os-articles/using-crash-logs/ but unfortunately, this relies on having stabs debug output, which doesn't happen with vbcc.
Hello all,
I am trying to get some info on leaked memory on an application I am working on. I would like to ask you if you are using memguard and if you know if it works fine on X5000. I am experiencing an ISI crash if I run memguard and have it enabled when I run my application.
The version I used with memguard was compiled with -gstabs, which as much as I know is necessary to get information about the line of the program when you check specific memory addresses. But I might be wrong as well.
Do you guys use spotless for debugging? It seems like an awesome app but couldn't make it work with simple C apps I create.
I compile my apps on my AmigaOS and with -gstabs on GCC, but when I load them in spotless nothing is happening. No code appears and I can't set break points anywhere.
The included test binary though seems to work fine.
Any more info on how to use it? The only alternative we have is GDB?
Hello guys,
I am trying to understand how I can use a crashlog to find were the problem is on my programs. Is there any documentation anywhere that gives some information on how to use that information? I checked the wiki.amigaos.net and couldn't find something there.
Hello any idea to look at Altivec registers contents? I have to debug some altivec code, I think to generate some nan followed by altivec crashes. Sadly in Grim Reaper aren't showed altivec registers.
Is there any workaround to look inside them?
Hi guys. So I am resorting to doing some debugging in GDB. Since I wish to step through some machine code as I don't have the source. Otherwise I would be using DB101. :-)
So I refreshed myself with some tutorials on here and set out to debug. I loaded up the GDB console in a shell. And loaded the binary in with a file command. As there is no main() symbol I can break at I broke it at _start which worked fine. I am also able to single step.
