|
Archives
D Programming
digitalmars.Ddigitalmars.D.bugs digitalmars.D.dtl digitalmars.D.ide digitalmars.D.dwt digitalmars.D.announce digitalmars.D.learn digitalmars.D.debugger D.gnu D C/C++ Programming
c++c++.announce c++.atl c++.beta c++.chat c++.command-line c++.dos c++.dos.16-bits c++.dos.32-bits c++.idde c++.mfc c++.rtl c++.stl c++.stl.hp c++.stl.port c++.stl.sgi c++.stlsoft c++.windows c++.windows.16-bits c++.windows.32-bits c++.wxwindows digitalmars.empire digitalmars.DMDScript electronics |
digitalmars.D - DMD generated exes' size differ from PE headers
I'm walking the PE header sections to find out the file size. I find the maximum PointerToRawData and add SizeOfRawData of the section to find where the exe ends. It works with the files I've tested. When compiling exe file with DMD 1.055 and -g there are additional four bytes after the last section. Why is that? Is SizeOfRawData wrong or there is something else at the end? Thanks Jan 26 2010
bobef wrote:I'm walking the PE header sections to find out the file size. I find the maximum PointerToRawData and add SizeOfRawData of the section to find where the exe ends. It works with the files I've tested. When compiling exe file with DMD 1.055 and -g there are additional four bytes after the last section. Why is that? Is SizeOfRawData wrong or there is something else at the end? Jan 26 2010
Hello bobef,I'm walking the PE header sections to find out the file size. I find the maximum PointerToRawData and add SizeOfRawData of the section to find where the exe ends. It works with the files I've tested. When compiling exe file with DMD 1.055 and -g there are additional four bytes after the last section. Why is that? Is SizeOfRawData wrong or there is something else at the end? Jan 26 2010
BCS Wrote:Hello bobef,I'm walking the PE header sections to find out the file size. I find the maximum PointerToRawData and add SizeOfRawData of the section to find where the exe ends. It works with the files I've tested. When compiling exe file with DMD 1.055 and -g there are additional four bytes after the last section. Why is that? Is SizeOfRawData wrong or there is something else at the end? Jan 27 2010
|