| Summary: failed call_external under Windows NT [message #10895] |
Mon, 09 February 1998 00:00 |
David Kastrup
Messages: 33
Registered: February 1998
|
Member |
|
|
Well, I though it might be nice to summarize the answers to my
request about call_external failing after 50-odd calls because of
exhausted memory under WinNT (IDL 5.03 running under Windows NT 4).
Here is the summary of all responses I received:
----
----
That's all folks. Unfortunately, none of the suggestions worked.
Anyhow, I've been able to find the problem myself after a lot of
hassle: I had been using a line looking like
s = call_external('r:/dll/dummy.dll','dummy');
It turns out that this must be
s = call_external('r:\dll\dummy.dll','dummy');
The ugly thing is that IDL *will* call the routine without
complaining. It will just not remember that it has alrady loaded the
DLL, and will load another copy of it the next time. After you filled
your memory with 50 copies of the DLL, it gives up.
A colleague of mine remarked that this might be the "solution" to a
question once appearing on this newsgroup, namely how to make IDL use
a newly-compiled DLL instead of an older copy, without restarting it.
Very funny.
--
David Kastrup Phone: +49-234-700-5570
Email: dak@neuroinformatik.ruhr-uni-bochum.de Fax: +49-234-709-4209
Institut f�r Neuroinformatik, Universit�tsstr. 150, 44780 Bochum, Germany
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
