Hi all,
I have a serious problem when calling a DLL procedure.
The DLL is a third party product (an API to a big relational data base) and is in deployment in the
production area in the company I am with on many systems.
It is used by many programms written in different languages (C, C++, Visual Basic).
Calling the DLL procedures with CP works well on some systems. On other systems I
get an error message or even a trap when I call the initialisation routine of the DLL
which has to be the first call before using the DLL.
The initialisation routine has an input parameter (a string), an output parameter (a pointer
to a string) and returns an integer value. I expect the parameter passing from CP to the
routine to contain no error because it works on some systems.
On some systems calling the initialisation routine produces a trap looking like this:
illegal memory read (ad = 15FEAB80H)
?(???(?(?(?(?(???(?(???(?(?(?(?? 01X
<system> (pc=7711E3BEH, fp=0028E5CCH)
<system> (pc=7711E022H, fp=0028E5E4H)
<system> (pc=74E914DCH, fp=0028E5F8H)
<system> (pc=7C342189H, fp=0028E640H)
<system> (pc=6DA140B0H, fp=64CA8000H)
This trap window looks different from the usual traps I get when I e.g. try to access memory with a NIL pointer.
Does anybody have an idea what the trap information tells ?
- does it tell my input string to the DLL procedure may be invalid ?
- does it tell the DLL code has an internal problem ?
- does it tell an invalid memory access with the output parameter ?
When I put a HALT statement right after the DLL call the HALT will not be executed.
It would be helpful to have any idea about what is going on when I want to ask the vendor of the DLL for a solution.
Thanks for any hints and best regards,
Rainer
---- To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to LISTSERV{([at]})nowhere.xy
Received on Sat Oct 06 2012 - 16:14:07 UTC