[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/25374] linking to msvc import library results in invalid IDT ent

From: martin at martin dot st
Subject: [Bug ld/25374] linking to msvc import library results in invalid IDT entry
Date: Sun, 12 Jan 2020 21:50:28 +0000


Martin Storsjö <martin at martin dot st> changed:

           What    |Removed                     |Added
                 CC|                            |martin at martin dot st

--- Comment #1 from Martin Storsjö <martin at martin dot st> ---
(In reply to Dan Raymond from comment #0)
> Examination of the .idata section in the MinGW DLL revealed that ILT and IAT
> tables were present for both the MSVC DLL and EXE.  The IDT entry (which
> contains pointers to the ILT and IAT) was correct for the MSVC DLL.  The IDT
> entry for the MSVC EXE, however, was incorrect.  The ILT and IAT pointers
> pointed to the NULL entries at the end of the tables rather than the first
> entries.

I was able to reproduce a similar issue when linking against two import
libraries for two DLLs (without involving the concept of EXEs exporting symbols
and import libraries for them).

My suspicion is that the synthesized import table chunks (when using msvc style
import libraries, where the linker needs to synthesize the import table
contents) aren't sorted correctly if there's more than one msvc style import
library involved.

You are receiving this mail because:
You are on the CC list for the bug.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]