X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
From: Andris Pavenis <pavenis AT latnet DOT lv>
To: djgpp-workers AT delorie DOT com
Subject: Re: Patches to build GDB 6.3
Date: Wed, 8 Dec 2004 12:12:27 +0200
User-Agent: KMail/1.7.1
References: <01c4c987$Blat.v2.2.2$52b9e920 AT zahav DOT net DOT il> <200412071838 DOT 09466 DOT pavenis AT latnet DOT lv> <01c4dc93$Blat.v2.2.2$796ce760 AT zahav DOT net DOT il>
In-Reply-To: <01c4dc93$Blat.v2.2.2$796ce760@zahav.net.il>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200412081212.27942.pavenis@latnet.lv>
X-Virus-Scanned: by amavisd-new at fgi.fi
Reply-To: djgpp-workers AT delorie DOT com

On Tuesday 07 December 2004 21:31, Eli Zaretskii wrote:
>
> I'm confused.  Could you please tell the entire history of the DWARF-2
> register numbering in DJGPP?  AFAIK, it didn't change since the first
> GCC version that supported DWARF-2 in DJGPP COFF executables, but you
> seem to imply that it already changed once, and that now we need to
> change it again.  What version(s) of GCC changed that?
>
> The only related change I'm aware of is the change in GDB which was
> made some time ago, to bring the DJGPP port of GDB in line with GCC
> and other x86 ports.  Again, you seem to say that we are now
> incompatible with GNU/Linux numbering?

There were problems (about 2 years ago) with C++ exceptions when DWARF2 
debugging information was requested. Some variant was found, that seemed to 
work Ok also with GDB, but only later was found that it was incorrect. As 
result we have had wrong register numbering there since release of first 
ports of DJGPP port of GCC-3.X.

So now I'm trying to fix up this mess. Biggest problem is that changing 
register numbering makes object files incomaptible. However perhaps only
C++ exceptions are affected. After rebuilding all C++ sources exceptions 
are catched normally.

Andris