🚀 go-pugleaf

> I am also very interested in this.
> 
> I am running gcc-2.2.2, on Domain/OS 10.3, but I still can't use debugging.
> Does gdb-4.7 work with the Apollo C compiler? Can gcc be made to generate
> debugging information that gdb understands?
> 
> I guess I should get gdb-4.7 and find out.

Well I don't know about sr10.3, but my guess is that gdb won't work on
any Apollo for Apollo COFF files.  It certainly doesn't under sr10.2.
As distributed, it doesn't even recognise that they are COFF files,
and since it only contains configuration files for using the Apollo
as a host machine, and not as a target machine, I suspect it isn't
intended to be able to debug Apollo executables, just read executables
compiled for other platforms.

However I am working on getting gdb working with Apollo debugging information.

Getting it to recognise that they are COFF files is trivial, and while
this can get gdb to load and execute a file with global symbols loaded
in, you don't get line numbers, function return values and probably don't
get structures and unions either (I haven't tested this) and if you set
a breakpoint the machine goes off to never-never land when the breakpoint
is reached.

Once I finish this I will work on getting gas (Not gcc, as gcc simply passes
the debugging information on to gas for it to process into the object file)
working with Apollo debugging information, unless, of course, somebody else
wants to do it, in which case they can use what I've learned. This would
be preferable, because I won't be able to get started on gas until the
second week of January.

Doing things during compile cycles of real life projects, I expect to finish
on gdb by the end of the coming weekend.
--
__________________________________________________________________________
troy@cbme.unsw.EDU.AU	Overworked, overcommited and always multitasking.
Patron of SNUB (Say NO to Unattended Bots)