RE: [GD-Windows] DLL initialization (was: Loading new DLLs on old Windows)

[Jon W. <hp...@mi...>]

Yeah, Windows is like that :-(

If it's a crash, you can look into the minidump facility that's built-into
Windows XP, but this error probably doesn't count as a catchable exception.
Does it say what the offending library is? Can you run a debug output spy
and capture information? If you can't even do that, I can't think of another
way to debug it.

Re-write your demo to load all shared libraries manually? :-)

Good luck!

Cheers,

			/ h+


-----Original Message-----
From: gam...@li...
[mailto:gam...@li...]On Behalf Of
Andras Balogh
Sent: Friday, February 13, 2004 9:21 AM
To: gam...@li...
Subject: Re: [GD-Windows] DLL initialization (was: Loading new DLLs on
old Windows)


Hi Jon,

The DLL exists (otherways the error code would be different), and it
also doesn't mess with UNICODE. The logs report that memory is also
sufficient.

Unfortunately, I can't use a debugger, as this error doesn't happen on
my machine. Actually, this program is just my tech demo. Many people
have tried it and I got a lot of positive feedbacks so far, but now
some guy told me that it breaks on his machine, giving this error
message... So I have to figure this out blindly..

Thanks,

Andras

Thursday, February 12, 2004, 9:10:43 PM, Jon Watte wrote:


> Typically this means that you're linking with a DLL that doesn't exist, or
> you're calling UNICODE functions without unicode support, or you're plain
> running out of memory. Do you have one of the machines available for
> debugging? WinDbg sometimes helps in debugging these things.

> Cheers,

>                         / h+


> -----Original Message-----
> From: gam...@li...
> [mailto:gam...@li...]On Behalf Of
> Andras Balogh
> Sent: Thursday, February 12, 2004 4:21 AM
> To: gam...@li...
> Subject: [GD-Windows] DLL initialization (was: Loading new DLLs on old
> Windows)


> My program supports dynamic loading of plugins. Every plugin
> represents a class, and resides in a separate DLL. Instead of
> exporting the class itself, I only export a factory function and
> provide a header file with the declaration of the pure virtual base
> class (ie. the interface). At runtime, I load the DLL and call the
> exported factory function, which instances an object and returns a
> pointer to the base class.

> This architecture works like a charm on most machines. However, on
> some configurations, my program reports the following: "Error Code
> 1114: A dynamic link library (DLL) initialization routine failed."

> But I have no clue why. Do I have to use DllMain? MSDN says it's only
> an optional entrypoint.. My DLLs are dynamically linked to the C/CPP
> run-time libraries.


> Thanks,

> Andras



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Gamedevlists-windows mailing list
Gam...@li...
https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows
Archives:
http://sourceforge.net/mailarchive/forum.php?forum_id=555