Date: Mon, 26 Jan 1998 18:53:43 -0800 (PST)
Message-Id: <199801270253.SAA29112@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: jsjogren AT algonet DOT se (Oscar Iommi Campbell), djgpp AT delorie DOT com
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Re: djgpp/rhide acting strange
Precedence: bulk

At 05:58  1/26/1998 GMT, Oscar Iommi Campbell wrote:
>I've been away from djgpp programming a few months, using VC++ 5.
>However today a I sat down to finish of an old GUI I was making in
>djgpp. The problem is when I debug some variables are said to be 'not
>available' though they exist right in front of my eyes. Sometimes they
>evaluate but to another value then the real one ('monitored' with
>fprint). Another bug also raises when I compile with -m486, in a place
>which isn't exactly a critical dangerous code place..
Check your compiler flags. Use `-g' and DO NOT use `-O*',
`-fomit-frame-pointer', or any other optimization options. They are known to
make debugging screwy.

If this fails to help, please post as small a piece of the source as
reproduces the problem, along with the exact flags you use to compile, RHIDE
version, etc.
>BTW, I've always runned rhide in a dosbox, it compiles 10-20 times
>slower in real dos!??.
Consider the possibilities described in FAQ sections 7.1 and 3.9.

Nate Eldredge
eldredge AT ap DOT net