X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
From: Andris Pavenis <pavenis AT latnet DOT lv>
To: Eli Zaretskii <eliz AT gnu DOT org>, dj AT delorie DOT com
Subject: Re: Patches to build GDB 6.3
Date: Tue, 7 Dec 2004 09:24:41 +0200
User-Agent: KMail/1.7.1
Cc: djgpp-workers AT delorie DOT com
References: <01c4c987$Blat.v2.2.2$52b9e920 AT zahav DOT net DOT il> <200411150943 DOT 28672 DOT pavenis AT latnet DOT lv> <01c4cb4a$Blat.v2.2.2$62af71a0 AT zahav DOT net DOT il>
In-Reply-To: <01c4cb4a$Blat.v2.2.2$62af71a0@zahav.net.il>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200412070924.41262.pavenis@latnet.lv>
X-Virus-Scanned: by amavisd-new at fgi.fi
Reply-To: djgpp-workers AT delorie DOT com

On Monday 15 November 2004 21:35, Eli Zaretskii wrote:
> > From: Andris Pavenis <pavenis AT latnet DOT lv>

> It didn't fail for me.  Please post the relevant fragment from the
> build session, so I could see the command that failed and the error
> message(s).
>
> > main (argc=0, argv=0x0) at gdb.c:30
> > 30        memset (&args, 0, sizeof args);
> > (top-gdb) n
> > During symbol reading, Incomplete CFI data; unspecified registers at
> > 0x0000174c.
>
> Yes, I see this, too.  Will look into this.

These problems (not one with observer.sh) with GDB-6.3 was caused not by any 
problem in it, but as I found in last days, by breakage off all recent 
version of DJGPP port of GCC in last 2 years. The breakage doesn't (I hope 
so) cause GCC compiled binaries to crash, but it introduces incompatibility 
with for example GDB due to unnecessary and incorrect change in 
gcc/config/i386/djgpp.h

I noticed it when tried to clean up this file from unnecassary stuff, to be 
able to submit changes for GCC. If I fix this problem, there is no more 
earlier mentioned problems with GDB-6.3. GDB-6.3 seemsto work OK both with 
rebuilt GCC-3.4.3 and GCC-4.0 20041202. However no more detailed tests 
are done yet.

The biggest problem is that fixing this problem makes GCC compiled object 
files incompatible perhaps only for C++ (which appears hopefully only as 
broken C++ exceptions in case of mixing object files).

So the question is what to do?

I could rebuild GCC-3.4.3 and maybe some other earlier GCC versions and 
reupload. But in this case we'll have above mentioned binary incompatibility.

Or we can do nothing now and fix the probloem for GCC-4.0 when it comes out.
The problem is that in that case we'll have problems debugging executables 
built with earlier GCC-3.X.X versions and GDB-6.3 and possibly with
GDB-6.1.1 

Andris