X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
Message-ID:	<5225575F.7060702@iki.fi>
Date:	Tue, 03 Sep 2013 06:28:31 +0300
From:	Andris Pavenis <andris DOT pavenis AT iki DOT fi>
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130805 Thunderbird/17.0.8
MIME-Version:	1.0
To:	djgpp AT delorie DOT com
CC:	Juan Manuel Guerrero <juan DOT guerrero AT gmx DOT de>
Subject:	Re: Used DWARF version for GCC-4.8.1
References:	<5224ADC3 DOT 6050608 AT iki DOT fi> <8751db7a-0f08-44d8-aa7c-33912e8c3db4 AT googlegroups DOT com>
In-Reply-To:	<8751db7a-0f08-44d8-aa7c-33912e8c3db4@googlegroups.com>
Reply-To:	djgpp AT delorie DOT com

On 09/02/2013 11:10 PM, Juan Manuel Guerrero wrote:
>
> I have given the new compiler a try using it with libiconv 1.14 that I am porting.  I have compiled with -g2 -O0 and I did not experienced the CTA issue anymore.  I also had no difficulties with the bt command, but the function stack was only 4 functions deep.  May be the debugged application that uses libiconv.a was not big enough to trigger the problem.
>
> I am also working on a port of gdb-7.6.1.  Are there any issues that may be considered to allow DWARF4 support for djgpp?  At least at a first glance of
> the configure script, there seems to be no switch to select the DWARF version that shall be supported by gdb.  Maybe a lot of time must be invested in this
> port to implement djgpp specific issues concerning DWARF4 support.  I do not know if this will happen with this gdb port.
>

You should be able to get DWARF4 with new build (for example -g3 -gdwarf-4). I guess one can after 
that try to debug GDB and see what is going wrong. The location where to put breakpoint inside GDB 
can easily be found by error message (can't compute CFA for this frame). After that it may become
clear which of GCC and GDB must be fixed (or both)

Andris

- Raw text -