This is the mail archive of the crossgcc@cygnus.com mailing list for the crossgcc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
My current setup is using binutils-2.9.1 and gcc-2.8.1 cross compiling for powerpc-eabi from a sunos4.1.4 machine. When using ld to link my files I am noticing that my first segment (defined in the program header) has a file offset of 0. This can be seen by running objdump --private-headers image.x image.x: file format elf32-powerpc Program Header: LOAD off 0x00000000 vaddr 0x00000000 paddr 0x00000000 align 2**16 filesz 0x0000a258 memsz 0x0000a258 flags rwx LOAD off 0x00010000 vaddr 0x00400000 paddr 0x0000a258 align 2**16 filesz 0x00000d34 memsz 0x00000d34 flags rw- LOAD off 0x00010d38 vaddr 0x00400d38 paddr 0x00400d38 align 2**16 filesz 0x00000000 memsz 0x00000884 flags rw- LOAD off 0x00020100 vaddr 0xfff00100 paddr 0xfff00100 align 2**16 filesz 0x00001300 memsz 0x00001300 flags r-x Dynamic Section: This is confusing a bdm debugging device that I am using. It is expecting the first section to start after the program and elf headers. In looking into the ELF backend BDF code I noticed flags that seem to allow you to put the program header and elf header into the first segment. In reading the ELF ABI it doesn't say that you can do that. At least that I can find. :) Is this really doing what I think its doing and if so why is it done? So far I been able to defeat this by running the linker by passing it the -N or -n flags. Thanks, Vaughan _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ New CrossGCC FAQ: http://www.objsw.com/CrossGCC _______________________________________________ To remove yourself from the crossgcc list, send mail to crossgcc-request@cygnus.com with the text 'unsubscribe' (without the quotes) in the body of the message.