Re: [Mingw-w64-public] Problems when building NT kernel drivers with GCC / LD

[ralph engels <ralphengels@gmail.com>]

i think most of it stems from binutils tools being geared towards linux 
driver development ? and since noone before has shown much interrest in 
developing drivers for windows using the gnu tools. I also think that 
there might be some pitfalls -> incompatible exception models for one 
(most mingw based compilers today use dwarf unwinders for 32 bit maybe a 
few who use sjlj) the problem with that is that atleast 32 bit windows 
cannot do anything with this exception model sjlj is a little better in 
that regard but still. If done in pure C or asm it could work if those 
options were avaliable but it does limit the scope i think.

Den 30-10-2022 kl. 08:06 skrev Martin Storsjö:
> On Sun, 30 Oct 2022, Pali Rohár wrote:
>
>> * LD --dynamicbase is not working correctly. If used for PE executables
>>  (not dynamic libraries) then it does *not* generate relocation info.
>>  And without relocation info in PE binary, it is not possible to
>>  relocate base address. Which makes dynamic base non-working.
>
> I don't know about the rest, but this one sounds familiar to me. But 
> IIRC this one was fixed semi-recently (1-2 years ago), while making 
> --dynamicbase the default.
>
> I think it was fixed in this binutils commit:
>
> commit 514b4e191d5f46de8e142fe216e677a35fa9c4bb
> Author: Jeremy Drake <sourceware-bugzilla@jdrake.com>
> Date:   Thu Aug 27 12:58:27 2020 +0100
>
>     Change the default characteristics of DLLs built by the linker to 
> more secure settings.
>
> This commit is included in binutils 2.36 and later.
>
> // Martin
>
> _______________________________________________
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public