On Fri, Feb 17, 2012 at 10:28 PM, Dmitry Timoshkov wrote:
> PE header marks the beginning of a PE module in memory, and it needs to be
> aligned on allocation granularity.
>
So it is.. Then thank you again Dmitry. :-)
--
*
[A very large, very cold, and extremely isolated planet.]
[ApertureScie
Pengyu CHEN wrote:
> > PE header needs to be aligned in a 64k boundary, and compiler fills
> > remaining space with zeros.
>
> Thank you Dmitry, and now I'm clear with that.
> Yet another question here. I've just check the msdn page and found 64K is
> actually the maximum possible value of Secti
On Fri, Feb 17, 2012 at 9:48 PM, Dmitry Timoshkov wrote:
> PE header needs to be aligned in a 64k boundary, and compiler fills
> remaining space with zeros.
Thank you Dmitry, and now I'm clear with that.
Yet another question here. I've just check the msdn page and found 64K is
actually the maximu
Pengyu CHEN wrote:
> Then I compiled them using 'winegcc a.c a.spec -shared -fPIC -m32', and
> then found the resulting file a.out.so is about 70KB in size:
> [pengyu@pengyu-Studio-1747 tmp]$ls a.out.so -l
> -rwxr-xr-x 1 pengyu users 75893 Feb 17 19:16 a.out.so
PE header needs to be aligned in a
Hello everyone,
I'm new here, and if I did/said something wrong, please point out instead
of throwing stones at me :-)
I'm currently developing stuffs with winelibs, and when building a shared
lib with winegcc, I find the generated file is weirdly large.
The example below illustrates my problem.
