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: Fri, 10 Dec 2004 11:02:21 +0200
User-Agent: KMail/1.7.1
References: <01c4c987$Blat.v2.2.2$52b9e920 AT zahav DOT net DOT il> <200412081212 DOT 27942 DOT pavenis AT latnet DOT lv> <01c4dd4c$Blat.v2.2.2$849c3820 AT zahav DOT net DOT il>
In-Reply-To: <01c4dd4c$Blat.v2.2.2$849c3820@zahav.net.il>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200412101102.21274.pavenis@latnet.lv>
X-Virus-Scanned: by amavisd-new at fgi.fi
Reply-To: djgpp-workers AT delorie DOT com

On Wednesday 08 December 2004 19:35, Eli Zaretskii wrote:
> > From: Andris Pavenis <pavenis AT latnet DOT lv>
> > Date: Wed, 8 Dec 2004 12:12:27 +0200
> >
> > 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.
>
> Are you saying that the C++ compiler uses (or used in the past) a
> different register numbering scheme than the C compiler?  Because I
> don't think I ever saw any such problems with C programs.

Register numbering used for call frame was different from one used by 
debugger. So it's also for C. However it perhaps causes runtime problem only 
with C++ exceptions. Also it breaks backtrace command in new versions of GDB 
for all languages. GDB-6.1.1 and earlier versions seemed to work OK. GDB-6.2 
and higher -  no more. Register numbering used for DWARF2 debugging 
information was Ok.

Andris