Danny Backx wrote:
> I would
> have expected it to report that the symbol I want to look up isn't
> present, because objdump says it has no symbols, but it does find it.
"objdump -t" dumps only the COFF symbol table, that is .obj-file-style
symbols, debug symbols, etc.; what you are looking at
Vincent R. wrote:
>> So Dave, question coundn't we manually change .idata section
>> characteristics for instance instead of disabling auto-import ?
>
>
> Ok I just tried to modify .idata section characteristics by removing write
> attributes and of course now I don't even have an error messag
On Thu, 2009-11-05 at 21:31 +0100, Danny Backx wrote:
> I've tested with my testapi application (see tools/dll) .
>
> On a DLL created with cegcc, the LoadLibrary system call fails with
> error ERROR_BAD_EXE_FORMAT (value 193).
>
> On a DLL created with MSVC by Vincent, LoadLibrary does succeed.
I've tested with my testapi application (see tools/dll) .
On a DLL created with cegcc, the LoadLibrary system call fails with
error ERROR_BAD_EXE_FORMAT (value 193).
On a DLL created with MSVC by Vincent, LoadLibrary does succeed. I would
have expected it to report that the symbol I want to look
