Debugging on os4

Howdy,
What is the best way/tools used on OS4 to debug c/c++ code?

When the code runs under windows or Linux it's all good, but in os4 on repeated launches it causes the machine to lock up or have dsi errors.

Any advice appreciated.

Thanks
Dave

Sad but truth, the best way to debug os4 binaries is good old "printf" way + serial debug to catch a crash logs (to have output even if machine freeze).

Of course, we do have some helpful tools, but .. i can't say they are mature enough and ready for _real everyday work_.

The best practice is just build the binary with debug symbols in (via -gstabs added to compiling line), then when it crashes, check on what line from stack-trace, and then, put prinfs all over the places to see, when it exactly crashes and so on.

If you mean do we have debuggers : then, GDB is out of question, our version only good for simple tests. old DB101 and current Spotless developed by Alfkil can be also used till some except, but still it's not like usage of fully blown debuggers on win32 :)

If you try to debug programs on a X5000 you are out of luck anyway. The stock kernel on a X5000 is broken and prevents any debugger (gdb, DB101 or Spotless) to work.

As kas1e says, printf/kprintf/IExec->DebugPrintF are your friends.

And maybe that helps you finding the problematic line of code after a crash: https://wiki.amigaos.net/wiki/Using_Crash-Logs_for_Debugging

@FlynnTheAvatar

Quote:

Is this something that whoever works on the Kernel knows about and is looking at? Sounds like a pretty major flaw.

It never worked to begin with.

It is a massive flaw.

We have been waiting for a necessary upgrade to the ELF.LIBRARY for too long now.

Though, I think it is coming very soon.

Behind the scenes, things are moving, though; slowly.