This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/19087] Overflowed address in dwarf debug line information
- From: "bjoern dot m dot haase at web dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 May 2005 14:12:09 -0000
- Subject: [Bug target/19087] Overflowed address in dwarf debug line information
- References: <20041220095410.19087.tsandnes@atmel.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From bjoern dot m dot haase at web dot de 2005-05-06 14:12 -------
Hi Torleif,
I have just had a look at PR19885 and I am having one additional question:
IIUC, the lable references, that eventually cause the overflow problems refer
to memory in form of "byte" addresses and not "word" addresses: I.e. the
offsets and address information you are finding in the elf files all are "byte"
addresses. Am I right?
In the asm outputs I have investigated so far, I realized that for the lable
references in the dwarf sections avr-gcc is allocating two bytes only. So in
case that these two bytes are filled with "byte" addresses instead of "word"
addresses, it is obvious that an overflow could not be avoided. The cleanest
solution then would be to redefine the debugging format such that within the
debugging sections for the dwarf symbols, gcc allocates four bytes for the
pointers. I fear, however, that this would be a major challenge since one would
probably need to rewrite a considerable portion of the dwarf-output-genenerator
in a target-specific fashion.
If I'm not too wrong, we probably won't have a short term solution for this PR.
Anyway, I think that this bug should be marked as NEW.
Yours,
Björn
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19087