reactos/sdk/cmake/init-section.lds

/* Make sure the INIT section is at the end of the module so we can reclaim the space */
SECTIONS
{
  INIT BLOCK(__section_alignment__) :
  {
    __init_start__ = . ;
    *(INIT)
    __init_end__ = . ;
  }
}
/*INSERT AFTER .reloc;*//*This is what we actually want to do, but do not dare due to LD bug ROSBE-154*/
INSERT AFTER .rsrc; /*This is what we do instead to at least fix CORE-14683*/
[CMAKE] Ensure the INIT section is placed at the end of a module. CORE-14683 For MSVC, marking the section as discardable will do this automatically. For GCC, we use a linker script that places it after the .reloc section (which should be the last "real" section, check ld --verbose output for the default linker script). This fixes what seems to be a regression from r55835 (!). 2019-06-29 19:24:28 +02:00			`/* Make sure the INIT section is at the end of the module so we can reclaim the space */`
			`SECTIONS`
			`{`
			`INIT BLOCK(__section_alignment__) :`
			`{`
			`__init_start__ = . ;`
			`*(INIT)`
			`__init_end__ = . ;`
			`}`
			`}`
[NTOSKRNL] Restore section layout for NTOSKRNL to fix BSOD regression CORE-14683 This version (after .rsrc) works different than the proper version I used for 0.4.12 (after .reloc). Inserting after .rsrc is actually not correct, but Thomas believes it can be used as a temporary trick to avoid random memory corruption upon relocations of the kernel, caused by ROSBE-154. I follow his advice, although when judging from practical tests only: as long as we limit this script to NTOSKRNL like I do for releases there have no negative consequences been observed in real life yet even with the proper version of 0.4.12. Up to now those problems have only been observed when used for drivers MODULE TYPE sdk/cmake/gcc.cmake as well, like it was tried for a moment in master 0.4.13-dev-609-g c4d8e2a6e9660c1f0d0d24877219baca443bbce0 Using for drivers immediately did lead to BSODs like CORE-16183 and therefore was mitigated in master by total disabling of the scripts for both, kernel and drivers in 0.4.13-dev-621-g 36e9a6f8ddc70018b55b0cad0b13128b1cbb60c2 To allow installing DVDWritenow without BSOD, we need the script at least for ntoskrnl! I committed this patch (after .rsrc) already into 0.4.13RC and 0.4.14RC. 2020-05-13 17:08:25 +02:00			`/INSERT AFTER .reloc;//This is what we actually want to do, but do not dare due to LD bug ROSBE-154/`
			`INSERT AFTER .rsrc; /This is what we do instead to at least fix CORE-14683/`