Hey,
binutils 2.36 now defaults to ASLR etc on Windows, so a cygwin compiled linker
will give you:
> peflags -v mydll.dll
mydll.dll: coff(0x2026[+executable_image,+line_nums_stripped,+bigaddr,+dll])
pe(0x0160[+high-entropy-va,+dynamicbase,+nxcompat])
Is this still problematic for cygwin?
The re
Christoph Reiter via Cygwin writes:
> binutils 2.36 now defaults to ASLR etc on Windows, so a cygwin compiled linker
> will give you:
>
>> peflags -v mydll.dll
> mydll.dll: coff(0x2026[+executable_image,+line_nums_stripped,+bigaddr,+dll])
> pe(0x0160[+high-entropy-va,+dynamicbase,+nxcompat])
>
> Is
On Sun, Feb 28, 2021 at 1:16 PM ASSI wrote:
>
> Christoph Reiter via Cygwin writes:
> > binutils 2.36 now defaults to ASLR etc on Windows, so a cygwin compiled
> > linker
> > will give you:
> >
> >> peflags -v mydll.dll
> > mydll.dll: coff(0x2026[+executable_image,+line_nums_stripped,+bigaddr,+dl
Christoph Reiter via Cygwin writes:
> MSYS2 builds all packages with ASLR since 6 months, so things look
> good.
That doesn't tell you all that much since you will have to wait for some
unfavorable address space layout constellation to appear for the problem
to announce itself and then you need so
On Sun, Feb 28, 2021 at 3:22 PM ASSI wrote:
>
> Christoph Reiter via Cygwin writes:
> > MSYS2 builds all packages with ASLR since 6 months, so things look
> > good.
>
> That doesn't tell you all that much since you will have to wait for some
> unfavorable address space layout constellation to appe
Christoph Reiter via Cygwin writes:
> To clarify: I was referring to non-cygwin targets. I had assumed you
> meant that by "cross compilation toolchain".
Then maybe I don't understand what you meant when you said you've built
MSys2 packages with ASLR on. The MingW-W64 toolchains indeed target
Win
On Sun, 28 Feb 2021, ASSI wrote:
> > Is this still problematic for cygwin?
>
> Yes it is and I'm currently figuring out how to best get rid of it in
> order to be able to update binutils (why this was ever allowed in
> without an accompanying configure option is a mystery to me).
Well, Microsoft'
Jeremy Drake via Cygwin writes:
> Well, Microsoft's LINK.EXE and LLVM's LLD have already been using these
> new defaults for some time. But I was surprised how quickly my patch was
> accepted/merged.
That was not under dispute in any of the discussions I've seen on this
topic.
> To clarify, defa
8 matches
Mail list logo