Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!cbmvax!valentin
From: valentin@cbmvax.commodore.com (Valentin Pepelea)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Help!  Need Suggestions on Debugging C Programs on Amiga
Keywords: C Debug Lattice Manx CPR Metascope dbx sdb
Message-ID: <14107@cbmvax.commodore.com>
Date: 30 Aug 90 19:05:24 GMT
References: <125148@pyramid.pyramid.com>
Reply-To: valentin@cbmvax (Valentin Pepelea)
Distribution: na
Organization: Commodore, West Chester, PA
Lines: 26

In article <125148@pyramid.pyramid.com> telam@pyrps5 (Thomas Elam) writes:
>
>Hello!  I'm fairly used to dbx, and somewhat used to sdb, but I can't
>even start my program under CPR without crashing (guruing) my Amiga.

CPR is know to require a *very* big stack. Increase it to 20000 or more
before starting it.

> Are there some tried and true steps to getting a program past the crucial
> steps, then keeping the debugging rolling quickly?  E.g., getting the
> program started, passing parameters properly to functions (right lengths),
> debugging without resorting to a lot of printf's or DPRINT's, etc.

I use KPrintF's with a terminal attached to the serial port rather than
printf's because, first of all, printf's are buffered. Thus your program may
crash, and you would not know how far it got to run. Another advantage of the
KPrintF's is that they do not need nor affect any other part of the system,
except the serial port. You may use KPrintF's even from interrupt code while
interrupts are disabled. (With Disable(), not or.w #0700,sr)

Valentin
-- 
The Goddess of democracy? "The tyrants     Name:    Valentin Pepelea
may distroy a statue,  but they cannot     Phone:   (215) 431-9327
kill a god."                               UseNet:  cbmvax!valentin@uunet.uu.net
             - Ancient Chinese Proverb     Claimer: I not Commodore spokesman be