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\System32\mshtml.tlb (6F140000-6F202000 -> 01640000)
|
(dll/ntdll/ldr/ldrutils.c:1377) Overlapping DLL: C:\ReactOS\System32\zipfldr.dll
|
zipfldr.dll has a base address and is properly handled by the script, but
mshtml.tlb is not yet!
0.4.15-dev-3034-gc0c9b14_mshtml_tlb_has_no_base_address.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-17718 comctl32 v5 and comctl32 v6 should have different base addresses
- Open
-
CORE-17635 GCC base address recalculation
- Resolved
-
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