From:	jkotland AT socs DOT uts DOT EDU DOT AU (Jerry Kotland)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: TIP OF THE WEEK
Date:	2 Sep 1997 19:38:28 +1000
Organization:	School of Computing Sciences, UTS
Lines:	29
Message-ID:	<5ugmqk$6n1@sally.socs.uts.EDU.AU>
References:	<5ue7v6$1eu AT freenet-news DOT carleton DOT ca> <340AAF2F DOT 162BE795 AT LSTM DOT Ruhr-UNI-Bochum DOT De>
NNTP-Posting-Host:	sally.socs.uts.edu.au
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Thomas Demmer <demmer AT LSTM DOT Ruhr-UNI-Bochum DOT De> writes:

>Paul Derbyshire wrote:
>[...]
>> Now, comb your disk for *.CHK files. For each one found, more it to the
>> screen: more file0001.chk for instance. (If that doesn't work you have a
>> weird/old DOS, and can try more <file0001.chk instead. Note the '<'
>> added.) Chances are one is your precious debugging output. Rename it,
>[...]
>Good idea. Nevertheless run SCANDISK/CHECKDSK once _before_  the faulty
>program, delete all FILE*.CHK. This decreases the files you have to more
>(or better: less ;-) afterwards.

Or you could write a small logging module, something that opens
a predefined logfile, writes your string and then closes it.

Something like
InitLog (char *logFileName);
LogMessage (char *format, ...); // vsprintf could implement this.

It works for me! :)

-Jerry.

-- 
* .,)  G'day from Jerry Kotland  Linux -      I thought i was wrong once
 (oo)  Computer Science Student  The Choice   but i was mistaken.
 (  (\ Univ of Tech Sydney, Oz.  of a GNU     -??
 -((-  jkotland AT socs DOT uts DOT edu DOT au  Generation 

- Raw text -