[Bug target/19087] Overflowed address in dwarf debug line information

2005-03-07 Thread tsandnes at atmel dot no

--- Additional Comments From tsandnes at atmel dot no  2005-03-08 07:07 
---
Subject: Re:  Overflowed address in dwarf debug line information


> I applied the GCC and binutil patches to ensure that my gcc is the same as 
> that 
> used in WinAVR Feb14/05 distribution.  I then built libc1.2.3 and clean built 
> my project.  Loaded it all into AS4.11 with the beta parser DLLs.  No 
> difference.
> 
> With the 32 bit dwarf address, line number info seems ok, local automatic 
> variables seem ok but the static and global variables all appear as invalid 
> locations when hovering over them.
> 
> I'll wait for any comments from Torleif as to whether this is at the AS4 
> parsing end or during one of the earlier stages (i.e. in GCC or binutils).

Great work!

If you could send me the object file , I could debug my 32-bit parser version 
to 
check out this problem with global/static data.

It is hard to make any statement on whether this is a parser or avr-gcc 
deficiency before investigating the object file.

Regards,

Torleif


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19087


[Bug debug/19087] Overflowed address in dwarf debug line information

2004-12-20 Thread tsandnes at atmel dot no

--- Additional Comments From tsandnes at atmel dot no  2004-12-20 13:40 
---
Subject: Re:  Overflowed address in dwarf debug line information

pinskia at gcc dot gnu dot org wrote:
> --- Additional Comments From pinskia at gcc dot gnu dot org  2004-12-20 
> 12:53 ---
> Can you attach a preprocessed source?

Hmm, That will probably be a problem.
I have just piled together a lot of generated code and a library to be able to 
create an object with this much program memory. Would the preprocessed source 
(of the file with main()) be of use anyway?

The library is a trick to fool avr-gcc into creating the object without failing.
If I just put it all in one file and try to compile it I get errors like these:

 >avr-gcc -Wall -gdwarf-2 -mmcu=atmega128 -O0 largeandsimple.c -o 
 >largeandsimple.elf
c:\DOCUME~1\tsandnes\LOCALS~1\Temp/ccew.s: Assembler messages:
c:\DOCUME~1\tsandnes\LOCALS~1\Temp/ccew.s:55075: Error: value of 66702 too 
large for field of 2 bytes at 16
c:\DOCUME~1\tsandnes\LOCALS~1\Temp/ccew.s:92562: Error: value of 66702 too 
large for field of 2 bytes at 52828
c:\DOCUME~1\tsandnes\LOCALS~1\Temp/ccew.s:54188: Error: value of 65542 too 
large for field of 2 bytes at 10009
...

Hmm, come to think of it, maybe I should report this as a bug too?

Torleif


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19087


[Bug target/19087] Overflowed address in dwarf debug line information

2004-12-20 Thread tsandnes at atmel dot no

--- Additional Comments From tsandnes at atmel dot no  2004-12-20 14:15 
---
Subject: Re:  Overflowed address in dwarf debug line information

pinskia at gcc dot gnu dot org wrote:
> --- Additional Comments From pinskia at gcc dot gnu dot org  2004-12-20 
> 14:05 ---
> Hmm, on the mainline I get an error about dwarf2 not being supported:
> t.c:1: error: target system does not support the "dwarf-2" debug format

avr-gcc must be built with dwarf support to be able to produce objects with 
dwarf2 debugging information.

It is probably nececssary to build the entire toolchain from scratch.

Something like this.

1 cd binutils
2  ./configure --target=avr-elf --with-dwarf2
3 gmake
4 gmake install
5 cd ../gcc
6 ./configure --enable-languages=c,c++ --target=avr --with-dwarf2
7 gmake
8 gmake install
9 cd ../avr-libc
10 ./configure --prefix=/usr/local
11 gmake
12 gmake install

Are you familiar with the AVR port?

Thanks for looking into this!

Torleif


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19087