[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
A difference between m68k-elf-gcc and m68k-elf-readelf.
From: |
Tom Burrell |
Subject: |
A difference between m68k-elf-gcc and m68k-elf-readelf. |
Date: |
Fri, 1 Aug 2003 13:23:10 -0700 |
I have been trying to contact anyone who can help.
I am using the gcc compiler vers 2.95.3. for the coldfire.
On small files (less than 64k load I think) the gcc and readelf agree.
on larger files (mine is 200k load) when the readelf gets to the debug-line
record for the second source file using this command line
m68k-elf-readelf --debug-dump=line coco.elf
it gives the error:
Extended opcode 2: set Address to 0x30020d6c
Extended opcreadelf: Warning: Only DWARF version 2 line info is currently
supported.
ode 1: End of Sequence
The debug-line data fro the larger file appears to be 4 byte aligned.
I have the same problem with my P&E debugger.
Who would know if this data is supposed to be aligned. P&E blames the gcc.
The gcc puts out non aligned data for the smaller files.
Any help would be appreciated,
Tom
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- A difference between m68k-elf-gcc and m68k-elf-readelf.,
Tom Burrell <=