On 1/7/2017 1:48 AM, Linda Zhang wrote:
> Hi LRN,
> Thanks for your information, I've tested that gcc -shared is OK, but dllwrap
> produced duplicate and wrong relocation info. It looks like dllwrap has been
> broken for many years. I'm submitting bug there.
> I've been using dllwrap to compile d
use I
remember MinGW told me to use it long time ago. and it provides more link
options than gcc -shared... What a pity...
Linda Zhang
From: LRN
Date: 2017-01-07 13:22
To: mingw-w64-public
Subject: Re: [Mingw-w64-public] [HELP] DLL relocation totally broken
On 07.01.2017 6:15, Linda Zh
On 07.01.2017 6:15, Linda Zhang wrote:
> OS: Win7 SP1
> Toolchain: Mingw-w64 i686-6.2.0-release-win32-dwarf-rt_v5-rev1
> GCC: 4.8.x - 6.2.0
> Binutils: 2.21 - 2.25.1
> MinGW: official and w64, 4.x - 5.0.1
> Threading and except: all (dw2/sjlj/seh + win32/posix)
>
> Consider a dll whose base addres
cated, resulting:
original: mov eax, 0; ...; test eax, eax; je xxx; mov [eax],
relocated: mov eax, 0xBAAD; ...; test eax, eax; je xxx; mov [eax], <-
SEGFAULT!
Linda Zhang
From: Norbert Pfeiler
Date: 2017-01-07 11:47
To: mingw-w64-public
Subject: Re: [Mingw-w64-public] [H
idk what the default should be or if anything is not working as expected
but i use -Wl,--dynamicbase to get a pass in the windows app cert kit
regarding ASLR
On Sat, Jan 7, 2017 at 4:19 AM Linda Zhang wrote:
> OS: Win7 SP1
> Toolchain: Mingw-w64 i686-6.2.0-release-win32-dwarf-rt_v5-rev1
> GCC: 4
OS: Win7 SP1
Toolchain: Mingw-w64 i686-6.2.0-release-win32-dwarf-rt_v5-rev1
GCC: 4.8.x - 6.2.0
Binutils: 2.21 - 2.25.1
MinGW: official and w64, 4.x - 5.0.1
Threading and except: all (dw2/sjlj/seh + win32/posix)
Consider a dll whose base address is overlapped with an existing module, so
that the o
