Im a little bit worried about the debugging... Great feature, but the thing with gdb is a little weird. I know that, when you compile unix apps under gcc, you have to compile with a special flag if you want to be able to debug with gdb... The extra flag does something to the code, puts in sometype of debug table? i dont know... it does something, and this adds to the overall executible, does it not?
Its also known that adding debuging features into a program can slow it down and make more resource hungry...
Is this the case for AmigaOS4 binaries? I would think that most users (and i admit AmigaOS users arnt most users
wouldnt want the gdb features, if it was going to comprimise performance in any way... I would think the gdb features would only be for beta testers/debuggers/developers of AmigaOS4 or their specific applications??
I just want to know, will adding gdb support to applications add any extra code or sometype of information to the executible so that gdb can track each execution of a statement in a program?
If something is added, is this considerable enough to slowdown the applications, either at load or run time?
Does it make it more memory hungry? <-- i guess that would be true even if only several killobyte of something was added to the application to provide this functionality...
Im pretty sure all of the above happens, and i wouldnt mind whilst i was debugging an application that i made. I just would want the above to be true for end user AmigaOS binaries, such as the TCP/IP stack or the kernel :} - although, i think i've just understood that maybe the article was just demonstrating what can be done whilst developer your own applications?
