Sender: brozzis AT mag00 DOT cedi DOT unipr DOT it
Message-Id: <33843664.65E4@mag00.cedi.unipr.it>
Date: Thu, 22 May 1997 14:04:52 +0200
From: Stefano Brozzi <brozzis AT mag00 DOT cedi DOT unipr DOT it>
Mime-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Weird behaviour and foggy description
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

I'm compiling a rather large project built for BC, and working if
compiled under BCC.
It claims it works even under Linux (GCC) and MSC.
It uses, for BCC version, direct video access. 
I've changed every such instruction to something DJGPP understands,
using or Screen*() functions or functions defined in conio.h.
I've converted every ASM statement in C code.
Compiler doesn't complain, but .exe doesn't work.
(So what ?! Debug it and shut up! - 
just imagining what you're thinking :)

I'm using RHIDE for this project (1.2c), debugging it and doing
step by step execution showed me it fails on strange lines, with
weird behaviour.

For example, something like

{ 
	int bar = 0:
	foo( bar );

If I watch the variable 'bar' (yes, after init or into the function 
itself) it gives strange values.

Sometimes the program SIGABRT or SIGSEGV in simple assignments...
so i started to think that debugging info isn't totally OK.

What could generate this mess ?
Which things should I check ?
If this code works on other compilers, what are the critical parts
that could be responable ?
Sorry for the foggy description, but the problems aren't concentrated on
a single point, but spread all over.

	TIA
	Stefano