Xref: utzoo comp.lang.c:28426 comp.unix.wizards:21791 alt.sources:1833 comp.sources.d:5261 misc.misc:9664
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!netcom!dsmythe
From: dsmythe@netcom.UUCP (Dave Smythe)
Newsgroups: comp.lang.c,comp.unix.wizards,alt.sources,comp.sources.d,misc.misc
Subject: Re: #define DEBUG... (using printf for debugging)
Message-ID: <11656@netcom.UUCP>
Date: 4 May 90 05:57:51 GMT
References: <11290@hoptoad.uucp> <40628@cornell.UUCP> <90123.152729CMH117@psuvm.psu.edu>
Organization: NetCom- The Bay Area's Public Access Unix System {408 249-0290 guest}
Lines: 9

It seems to me that if you want to go the instrumentation route, as opposed
to the debugger route, then you might want to look at the dbugsys package
(I think that there were at least 2 kinds) posted a while back to c.s.misc
or c.s.unix.  If I recall correctly, it does all of that kind of DEBUG stuff
as well as giving you run-time control of the level of debugging info that
you want to see (foo -x4 , or something like that).  There were quite a
variety of functions there for many other purposes as well.

D