Date: Thu, 9 Sep 1999 09:13:39 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: bowman <bowman AT montana DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: DJGPP/RSXNTDJ vs Mingw32
In-Reply-To: <7_tB3.1426$vW1.7257@newsfeed.slurp.net>
Message-ID: <Pine.SUN.3.91.990909091315.6646A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 8 Sep 1999, bowman wrote:

> As far as debugging, Kernighan & Pike, in  _The Practice of Programming_ ,
> mention the use the debugger to get the backtrace,  and look at a few
> variables when a program dumps core. Otherwise, they find printf  and other
> debug statement compiled in generates a lot more meaningful information.

_The Practice of Programming_ is a wonderful book, but the above is
IMHO one of its few misses: they never mention the bugs where data is
overwritten or accessed when the programmer thinks it shouldn't.  Bugs
like these are virtually impossible to find without a debugger that
supports data-read and data-write breakpoints.