Details
-
New Feature
-
Resolution: Unresolved
-
Trivial
-
None
-
None
Description
Although we just regenerated the GCC base addresses in 0.4.15-dev-2997-gc6d08c4 we do still see some relocation issues afterwards in between our own (and not 3rd party!) dlls.
E.g:
(dll/ntdll/ldr/ldrutils.c:1338) LDR: LdrpMapDll Relocating Image Name C:\ReactOS\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.2600.2982_none_deadbeef\comctl32.dll (7BC80000-7BE70000 -> 00630000)
|
(dll/ntdll/ldr/ldrutils.c:1377) Overlapping DLL: C:\ReactOS\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.2600.2982_none_deadbeef\comctl32.dll
|
0.4.15-dev-3034-gc0c9b14_comctl32_v5_vs_v6_collision.log
(To see such stuff we ofc have to enable the logging like in 0.4.15-dev-2707-gd042f51, I do explicitly mention that because there was some pressure to silence those again, so please double-check in case you want to "resolve" this ticket!)
Attachments
Issue Links
- relates to
-
CORE-17635 GCC base address recalculation
- Resolved
-
CORE-17717 The python script for regenerating the GCC base addresses does not properly cover mshtml.tlb yet
- Untriaged
-
CORE-14831 CORE-11382 addendum: fix 3+1 remaining "XYZ has no base address", The python script for regenerating the GCC base addresses does not properly cover fusion, fusion1_1, fusion2_0, localspl_apitest.dll
- Resolved