Path: utzoo!mnetor!uunet!husc6!mailrus!ames!pasteur!ucbvax!RITVAX.BITNET!LMB7421 From: LMB7421@RITVAX.BITNET Newsgroups: comp.sys.apple Subject: APW C debugging question Message-ID: <8805081322.aa03880@SMOKE.BRL.ARPA> Date: 8 May 88 20:23:00 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 26 >From: "A. Flora-Holmquist">Subject: APW C debugging question >I am a new IIgs programmer and purchased the APW shell, C compiler, and >APW debugger. The debugger is a machine level debugger, the C compiler >to the best of my reading does not/will not produce an assembly listing. >If I need to debug a C program it appears that sprinkling DrawCString >in the code is my only choice. Have I missed something obvious in the >APW documentation that addresses debugging C programs with the APW >debugger? Any hints? It seems so obvious that a compiler should support >some debugger that I can't believe the APW C compiler/APW debugger >combination is useless. The executable code is what you use in the debugger...there isn't a macro assembly debugger (yet), so you have to know mini-assembler...I usually debug using certain key code...toolbox calls, ProDOS calls, compares, etc. The debugger appears to be built for low-level assembly freaks (no, this isn't a cutdown on people programming in assembly or, god forbid, machine language - I do it myself :-), however, a C program is within reason. >Al Flora-Holmquist >ihnp4!ihlpl!nala Les Barstow LMB7421@RITVAX.BITNET rutgers!rochester!ritcv!ultb!lmb7421.UUCP 292 Kimball Drive Rochester, NY 14623 .USSnail