search for: _messageboxa

...hing that is still missing that sticks out like a sore thumb In the actual imports of the functions the objects are very different As you can see lib.exe generates a very simple function import object. IMPORT_OBJECT[1-N] -> contains an IMPORT_OBJECT_HEADER and DATA data example -> _MessageBoxA.USER32.dll dlltool however doesn't create an import object but infact has a complete IMAGE_FILE IMPORT_OBJECT[1-N] -> contains an IMAGE_FILE_HEADER and is a full object with SECTIONS the .text section has the stub code. the .idata$6 section has the name of the function it...

After some more digging and creating a few testcases in lld I have narrowed it down to The fact that dlltool generates Contents of section .idata$7: 0000 55534552 33322e64 6c6c0000 USER32.dll.. Where as lld expects Contents of section .idata$6: 0000 55534552 33322e64 6c6c0000 USER32.dll.. I recreated the hello64.test using dlltool for the lib and here is the asm dump of

...ticks out like a sore thumb > In the actual imports of the functions the objects are very different > > As you can see lib.exe generates a very simple function import object. > > IMPORT_OBJECT[1-N] > -> contains an IMPORT_OBJECT_HEADER and DATA > data example -> _MessageBoxA.USER32.dll > > dlltool however doesn't create an import object but infact has a complete > IMAGE_FILE > > IMPORT_OBJECT[1-N] > -> contains an IMAGE_FILE_HEADER and is a full object with SECTIONS > the .text section has the stub code. > the .idata$6 secti...