philip@cel.cummins.com (Philip D. Pokorny) (06/22/91)
Someone from Tandem writes: > I'm a gcc neophyte so here goes some dumb questions. > > Is there any way to get gcc to support source level debugging on Apollo > (dbx or gdb)? The factory version has -g disabled. If your intent is to develop code that runs on the Apollo, why not just use the Apollo C compiler and debugger supplied with the system? The 68000 compiler generates very good code and the 'dde' debugger is one of the best you'll find these days for source level debugging. Someone told me that there is no C compiler that comes free with the Domain/OS. Can someone confirm or deny that? Also, does 'dde' come free with the OS? (Perhaps your local Apollo rep. can help.) I personally use the Apollo C and DDE combination regularly and delight in showing it to people used to PC environments... It blows them away when I show them the things DDE can do... (Dump entire pointer linked structers with one command, complete debugging control from the mouse, watchpoints (break when a variable changes value), remote machine debugging (debug programs running on OTHER nodes), attach to and debug processes that are ALREADY running, and many more.) That last one is especially neat for getting rid of hung programs. Attach to the running program, load the status return variable with something like '0x40004' (reference to illegal address) and let it go. Kills processes even when kill -9 won't. Sincerely, Philip D. Pokorny philip@cel.cummins.com :)
rees@pisa.citi.umich.edu (Jim Rees) (06/25/91)
In article <9106211940.AA00946@cel.cummins.com>, philip@cel.cummins.com (Philip D. Pokorny) writes:
That last one is especially neat for getting rid of hung
programs. Attach to the running program, load the status return
variable with something like '0x40004' (reference to illegal
address) and let it go.
Much more fun is 0x220009.