Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!samsung!umich!umeecs!msi-s0.msi.umn.edu!cs.umn.edu!thelake!steve
From: steve@thelake.mn.org (Steve Yelvington)
Newsgroups: comp.sys.atari.st
Subject: Re: Re: Debugging Sozobon C Programs
Message-ID: <A1271862539@thelake.mn.org>
Date: 11 Aug 90 14:30:30 GMT
References: <1990Aug11.032802.4683@cunixf.cc.columbia.edu>
Organization: Otter Lake Leisure Society
Lines: 25
X-Member-Of:  STdNET
X-Bad-Pun:    There's no place like Nome for the Hollandaise.

[In article <1990Aug11.032802.4683@cunixf.cc.columbia.edu>,
     rjw@cunixa.cc.columbia.edu (Ricky J Witter) writes ... ]

> OK, I've got Sozobon C set up (with gulam, of course).  I've written a
> couple little programs to make sure it works.  Now, I run into some run
> time errors.  So my question is:  what do you use to debug your
> programs?  Is there something similar to dbx available on the ST?  Of
> course, I'm most interested in hearing of PD/shareware debuggers, but
> what do you experts out there recommend?  Thanks to all...
> 
> rick

I use the brute-force method:


#define DEBUG(x)	x  /* x */

DEBUG(fprintf(stderr,"<<File %s Line %d>>\n",__FILE__,__LINE__));

et cetera.  You also could use the Sozobon debugger, sdb, available from
the Panarthea file server or by FTP from atari.archive.umich.edu. I have
not made use of it.
-- 
   Steve Yelvington at the (rain-replenished) lake in Minnesota
   steve@thelake.mn.org