Hi,
In my romimage with linuxbios+etherboot payload, I do not see any section header, whereas in an EPIA romimage which I got from forum seems to have EPIA section headers. Should this be OK ? Should there be some problem with the build,etc? Or it is just fine.. ****readelf -a O/P of my romimage with linuxbios+etherboot payload***** ELF Header: Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: EXEC (Executable file) Machine: Intel 80386 Version: 0x1 Entry point address: 0x20000 Start of program headers: 52 (bytes into file) Start of section headers: 0 (bytes into file) Flags: 0x0 Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 2 Size of section headers: 0 (bytes) Number of section headers: 0 Section header string table index: 0
There are no sections in this file.
Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align NOTE 0x000074 0x00000074 0x00000074 0x0003c 0x0003c RWE 0 LOAD 0x0000b0 0x00020000 0x00020000 0x03dd9 0x12faf RWE 0
There is no dynamic segment in this file.
There are no relocations in this file.
There are no unwind sections in this file. ****readelf -a O/P of my ROM image*****
****readelf -a O/P of my EPIA romimage with linuxbios+etherboot payload*****
ELF Header: Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: EXEC (Executable file) Machine: Intel 80386 Version: 0x1 Entry point address: 0x94000 Start of program headers: 52 (bytes into file) Start of section headers: 13956 (bytes into file) Flags: 0x0 Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 1 Size of section headers: 40 (bytes) Number of section headers: 6 Section header string table index: 5
Section Headers: [Nr] Name Type Addr Off Size ES Flg Lk Inf Al [ 0] NULL 00000000 000000 000000 00 0 0 0 [ 1] .text PROGBITS 00094000 000060 002ecc 00 WAX 0 0 4 [ 2] .rodata PROGBITS 00096ee0 002f40 000653 00 A 0 0 32 [ 3] .data PROGBITS 00097540 0035a0 0000b4 00 WA 0 0 32 [ 4] .bss NOBITS 00097600 003660 003b28 00 WA 0 0 32 [ 5] .shstrtab STRTAB 00000000 003660 000024 00 0 0 1 Key to Flags: W (write), A (alloc), X (execute), M (merge), S (strings) I (info), L (link order), G (group), x (unknown) O (extra OS processing required) o (OS specific), p (processor specific)
Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x000060 0x00094000 0x00094000 0x035f4 0x07128 RWE 0x20
Section to Segment mapping: Segment Sections... 00 .text .rodata .data .bss
There is no dynamic segment in this file.
There are no relocations in this file.
There are no unwind sections in this file.
No version information found in this file. *****End******
Regards Deepak
For this level of debugging I usually use xxd. See what you see with that.
ron
This seems to be hexdump utility like od -cx, what exactly one should look for in this to convince onself that the romimage is OK, any pointers ?
----- Original Message ----- From: "ron minnich" rminnich@lanl.gov To: dkotian3@vsnl.net Cc: linuxbios@clustermatic.org Sent: Monday, May 05, 2003 8:02 PM Subject: Re: readelf O/P of romiage(linuxbios+etherboot) question
For this level of debugging I usually use xxd. See what you see with that.
ron
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
On Tue, 6 May 2003, Deepak Kotian wrote:
This seems to be hexdump utility like od -cx, what exactly one should look for in this to convince onself that the romimage is OK, any pointers ?
Look at the image that works and the one that does not and you will see what you need to look for.
I am being a bit obscure here because I feel you need to spend some time working this out.
thanks
ron