[ros-dev] Proposal to change .sym files

[Hartmut Birr]

Ge van Geldorp schrieb:

>>From: Hartmut Birr
>>
>>I'm not sure if you mean objcopy instead of objdump. Objcopy
>>for pe images isn't usable, because it changes the file and
>>section allignments. I think that we need a tool which creates
>>our new debug section as coff object file from the *.nostriped.*
>>and that we need our own linker scripts which adds the section
>>at the correct position within the image. This needs also a
>>little change in freeldr, because the symbol section must be
>>located after the bss section in ntoskrnl.   
>>    
>>
>
>This is getting a bit over my head, I'm no hero with COFF, linker scripts
>and binutils in general. If I code the generation of the basic symbol file,
>would someone else be able (and willing) to change it to a COFF object file
>and do the linker magic?
>
>Gé van Geldorp.
>
>
>_______________________________________________
>Ros-dev mailing list
>Ros-dev at reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-dev
>
>
>  
>
Hi,

the coff format is very simple if no relocation and debug infos are 
needed. A good starting point is http://www.delorie.com/djgpp/doc/coff. 
I've add a little diff. Rsym puts each symbol info in a file named 
symbol.coff. Ntoskrnl is build with the symbol section. While inspecting 
ntoskrnl.exe, I've found some other bugs. Ntoskrnl.exe contains always a 
.stab and a .stabstr section. There exist relocation entries for the 
.stab and .stabstr section. There exist relocation entries for addresses 
after the end of the image.

- Hartmut


-------------- next part --------------
A non-text attachment was scrubbed...
Name: rossym.zip
Type: application/x-zip-compressed
Size: 1715 bytes
Desc: not available
Url : http://reactos.com:8080/pipermail/ros-dev/attachments/20050114/ff0a529d/rossym.bin