This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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



------- Comment #23 from eweddington at cso dot atmel dot com  2006-09-19 21:54 -------
(In reply to comment #20)
> I suggest that this change should be accompanied by another indication in
> the output that tells the ELF/DWARF-2 consumer about the changed pointer
> size.  Otherwise the consumer will experience "funny" behaviour.
> 
> While there are many ELF fields available that are otherwise unused on
> this architecture (like the OS or ABI fields), there doesn't seem to exist
> any practical way to modify their contents through the assembler/linker
> interface.  Thus, and after checking other GCC code like the section
> ".note.GNU-stack" suggested at the end of varasm.c, I think adding something
> like
> 
> named_section_flags (".note.DWARF2-32", SECTION_DEBUG);
> 
> to function avr_file_end() in gcc/config/avr/avr.c appears to be a suitable
> way to me to flag this information to the potential consumer.

Joerg,
I've been trying this, but something strange is going on. On the linker command
line, I specify for it to create a map file. I can correctly see the new
section, .note.DWARF2-32, in the map file. However, when I use avr-objdump on
the resulting ELF file, the section looks like it is not there. 

So can the linker show the section when it generates the map file, but then
remove the section, because the section is empty, when it does the final
generation of the ELF file?

Thanks
Eric


-- 


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]