From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: (Newbie Alert) RHIDE lies in debugging?
Date: 23 Aug 2000 07:48:21 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 17
Message-ID: <8nvvk5$hst$1@nets3.rz.RWTH-Aachen.DE>
References: <39a34d59 DOT 4345588 AT news DOT canterbury DOT ac DOT nz>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 967016901 18333 137.226.32.75 (23 Aug 2000 07:48:21 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 23 Aug 2000 07:48:21 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Greg Smith <g DOT smith AT chem DOT canterbury DOT ac DOT nz> wrote:
> I'm trying to use RHIDE to debug some code for DJGPP which looks a bit
> like this:

This is by far not precise enough to give a helpful response.  We'll
need compilable code (minimized to the bare necessities before
posting, please) to be able to test this out.

> Using the debugger to watch B, the problem seems to be that B is true
> but C isn't being evaluated. So is RHIDE lying? 

The debugger can be confused, sometimes, about the values of certain
variables in highly optimized code which are currently kept in
registers during execution.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.