Prev: Mixed code - Crashes in Release Mode
Next: Printing from Console Application
From: Pavel A. on 22 Aug 2008 12:37
Depends can trace your test app with your dll
(it hooks GetProcAddress or whatever).

--PA



Vincent Fatica wrote:
> On Fri, 22 Aug 2008 09:35:23 +0300, "Alex Blekhman" <tkfx.REMOVE(a)yahoo.com>
> wrote:
>
>> "Vincent Fatica" wrote:
>>> When I do that, it builds OK (no warnings or .CRT section) but
>>> it bombs when the host app loads it:
>>>
>>> R3604: An application has made an attempt to load the C runtime
>>> library incorrectly.
>> This is the clear sign that CRT crept in somewhere in your DLL.
>> Check your own and 3rd party code for "#pragma comment(lib, ...)"
>> directives. Also, you can open the DLL with Dependency Walker to
>> figure out what function is required from CRT.
>
> My DLL (together with several others) is a "plugin", not linked to the host app,
> but loaded after startup. It doesn't show up in depends. Can I do anything
> about that?
From: Vincent Fatica on 22 Aug 2008 16:02
On Fri, 22 Aug 2008 19:37:38 +0300, "Pavel A." <pavel_a(a)NOfastmailNO.fm> wrote:

>Depends can trace your test app with your dll
>(it hooks GetProcAddress or whatever).
>>
>> My DLL (together with several others) is a "plugin", not linked to the host app,
>> but loaded after startup. It doesn't show up in depends. Can I do anything
>> about that?

The host app loads a half-dozen plugins (DLLs) just after it starts up. I added
the directory where they reside to depends's collection of paths. None of them
show up. ... any ideas?
--
- Vince
First  |  Prev  | 
Pages: 1 2 3 4 5
Prev: Mixed code - Crashes in Release Mode
Next: Printing from Console Application