From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: gdb problem or just silly me - please help
Date:	Wed, 26 Apr 2000 09:56:47 +0200
Organization:	NetVision Israel
Lines:	15
Message-ID:	<3906A13F.4A2BB361@is.elta.co.il>
References:	<39047BEE DOT 306C88F AT jps DOT net> <Pine DOT SUN DOT 3 DOT 91 DOT 1000425112446 DOT 23128H-100000 AT is> <hqgcgs000nrggsam2ctcugvva7jeiks83l AT 4ax DOT com>
NNTP-Posting-Host:	ras1-p70.rvt.netvision.net.il
Mime-Version:	1.0
X-Trace:	news.netvision.net.il 956732186 25751 62.0.172.72 (26 Apr 2000 06:56:26 GMT)
X-Complaints-To:	abuse AT netvision DOT net DOT il
NNTP-Posting-Date:	26 Apr 2000 06:56:26 GMT
X-Mailer:	Mozilla 4.7 [en] (Win98; I)
X-Accept-Language:	en,ru,hebrew
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Damian Yerrick wrote:
> 
> On Tue, 25 Apr 2000 11:25:19 +0200 (IST), Eli Zaretskii
> <eliz AT is DOT elta DOT co DOT il> wrote:
> 
> >There's nothing wrong with printf debugging
> 
> Unless the printf() family function itself crashes the program.  This
> happens to me all the time when porting Allegro programs from DJGPP to
> Windows, as DirectX is somewhat finicky about when the screen can be
> drawn on.

This simply means that you need to use another function, not the literal
printf, but the principles remain the same.  For example, when debugging code
that cannot stand a DOS call, I use cprintf or cputs instead of printf.

- Raw text -