X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
Message-ID:	<520AF974.5040901@iki.fi>
Date:	Wed, 14 Aug 2013 06:28:52 +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: Programs compiled with gcc481 cannot be debugged with gdb.
References:	<51B36263 DOT 6080309 AT gmx DOT de> <51B41437 DOT 6070003 AT iki DOT fi> <52093221 DOT 9010206 AT iki DOT fi> <520A965C DOT 400 AT gmx DOT de>
In-Reply-To:	<520A965C.400@gmx.de>
Reply-To:	djgpp AT delorie DOT com

On 08/13/2013 11:26 PM, Juan Manuel Guerrero wrote:
>
> Yes, this seems to be the reason.  I was able to step through the code compiled with
> gcc481 if I use -gdwarf-2 flag.  Now , the question arises, shall djgpp also use DWARF4?
> How much work it will be to implement this?
>

I was also able to reproduce the same problem with gcc-4.6.3 with specifying
DWARF-3 debugging info from command line (-gdwarf-3). Also DWARF3 does not seem
to be OK

There also seems to be some more problems with displaying back-trace in GDB even if
DWARF-2 debugging info is being used.

For testing I tried to run for example xgcc.exe from gcc build tree under GDB (at least
it's real big enough executable instead of small examples)

For some targets GCC defaults to DWARF2 debugging info using some tricks with gcc spec
macros. Maybe we should use something similar. It would of course be better to actually
fix the problem

Andris

PS. If You are interested, You can also try recent 2013-08.11 snapshot of GCC for testing:
             http://ap1.pp.fi/djgpp/gcc/test/4.9.0-20130811/

- Raw text -