From:	Vik Heyndrickx <Vik DOT Heyndrickx AT rug DOT ac DOT be>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: djgpp/rhide acting strange
Date:	Tue, 27 Jan 1998 09:05:09 +0100
Organization:	University of Ghent, Belgium
Lines:	30
Message-ID:	<34CD9535.5AB@rug.ac.be>
References:	<34ccccb7 DOT 128929 AT news DOT algonet DOT se>
NNTP-Posting-Host:	eduserv1.rug.ac.be
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

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..
> 
> Has my djgpp/rhide freaked out somehow??
 
No :-)
Compile your code without optimizations.
In the past it was said that compilers could not optimize the code and
produce debugging information. Stallman and Kenner were able to
integrate both at the same time in the gnu compiler which djgpp uses.
But some sacrifices had to be made. This means that local variables can
get "optimized out" and that they can acquire other values other than
the value that was last explicitely assigned to them.

> BTW, I've always runned rhide in a dosbox, it compiles 10-20 times
> slower in real dos!??.

use SMARTDRV.EXE

-- 
 \ Vik /-_-_-_-_-_-_/   
  \___/ Heyndrickx /          
   \ /-_-_-_-_-_-_/

- Raw text -