I was trying to work out how Wine loads Windows executables. I have asked this question on Stack Exchange
http://reverseengineering.stackexchange ... tions-afte
I am wondering why Wine inserts different data than Windows when loading executables in memory. Also, if you happen to know the answer to my question on Stack Exchange plase reply.
Why Wine inserts different data when loading executables
Re: Why Wine inserts different data when loading executables
bidos
This is a very abridged version. There is a lot of stuff that happens in background.
Wine is a twist on the standard Linux/BSD/Unix dynamic binary loader. You are free to read loader.c in in wine source code.
We forbid testing with game cracks for the issue you came across. Many do alterations to items forbin to touch due to be undocumented areas of window or make presume that are in fact incorrect. Import Table RVA and IAT RVA addresses not meant to be static locations. The fact Windows address randomization does not work on everything is why patching those with fixed values would have worked in the first place. Broken address randomization does not exist in Windows 8. So a log of badly coded game cracks go splat on Windows 8 as well.
bigos wine is very much its own version of Windows. Wine emulates only as much of Windows behavior to make applications run. Please note we don't count badly coded game or software cracks as applications.
Wine old name Wine Is Not a Emulator. Yes wine emulates particular things but other areas its a replacement to a normal binary loader.
http://www.winehq.org/docs/winedev-guide/x2834I was trying to work out how Wine loads Windows executables.
This is a very abridged version. There is a lot of stuff that happens in background.
Wine is a twist on the standard Linux/BSD/Unix dynamic binary loader. You are free to read loader.c in in wine source code.
When it comes to address so do different versions of Windows.I am wondering why Wine inserts different data than Windows when loading executables in memory
We forbid testing with game cracks for the issue you came across. Many do alterations to items forbin to touch due to be undocumented areas of window or make presume that are in fact incorrect. Import Table RVA and IAT RVA addresses not meant to be static locations. The fact Windows address randomization does not work on everything is why patching those with fixed values would have worked in the first place. Broken address randomization does not exist in Windows 8. So a log of badly coded game cracks go splat on Windows 8 as well.
bigos wine is very much its own version of Windows. Wine emulates only as much of Windows behavior to make applications run. Please note we don't count badly coded game or software cracks as applications.
Wine old name Wine Is Not a Emulator. Yes wine emulates particular things but other areas its a replacement to a normal binary loader.
Re: Why Wine inserts different data when loading executables
there several loader.c files in the source. Which one you have in mind.oiaohm wrote: You are free to read loader.c in in wine source code.
I just want to understand process of loading a binary in memory. There some problems with loading of .rdata section that I do not understand.Wine old name Wine Is Not a Emulator. Yes wine emulates particular things but other areas its a replacement to a normal binary loader.
