From: Andris <pavenis AT lanet DOT lv>
Organization: Pavenis
To: djgpp AT delorie DOT com, Andrew Cottrell <andnews AT ihug DOT com DOT oz DOT au>
Subject: Re: debbuging with rhide. NOT. :(
Date: Mon, 25 Nov 2002 09:31:08 +0200
User-Agent: KMail/1.5
References: <CFN375840760659722 AT news DOT neti DOT ee> <CFN375844323652778 AT news DOT neti DOT ee> <po31uus92orh4l6r1jm02ov44qgjakjovk AT 4ax DOT com>
In-Reply-To: <po31uus92orh4l6r1jm02ov44qgjakjovk@4ax.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200211250931.08189.pavenis@lanet.lv>
Reply-To: djgpp AT delorie DOT com

On Sunday 24 November 2002 10:41, Andrew Cottrell wrote:
>
> If you are using C++ make sure you do not mix object files from
> different GCC versions, even 3.1 to 3.2 is different. C objects as far
> as I know are okay between the major versions, ie you can mix 3.1 and
> 3.2 C objects.

I haven't yet met problems with DJGPP, but I know one example where
C sources compiled with different GCC versions caused problems
for me:  Linux kernel versions 2.4.1[89] with RTAI patches.

I know it's not a good example, as it uses many gcc specific extensions,
but anyway. At least compiling kernel with gcc-2.95.3 and some of loadable 
module with gcc-3.2 (or opposite direction) is rather sure way how to get 
kernel OOPSes. Using each of these compilers alone in both places seems to be 
Ok.

So maybe there are problems waiting for victim also for DJGPP ...
(However I'm not sure).

Andris