Skip to first unread message
pvlis...@gmail.com
Dec 11, 2012, 6:19:40 AM12/11/12
to jniwrapp...@teamdev.com
Hello all.
We are using the native Hook functionality of JNIWrapper/WinPACK and more specifically the Hook.CALLWNDPROC
in order to be able to communicate with other native applications by exchanging Window Handle messages.
We seem to have a problem though that some of these executables fail on close, with an error such as :
The instruction at "0x00b852e9" referenced memory at '0x00b900bb'. The memory could not be "read". Click on OK to terminate the program.
The problem seems to occur at Windows XP and Windows Server 2003 machines, while on Windows 7 and Windows Server 2008 the problem does not occur.
We are running under jre 1.7.0_09 (x32bit) and using jniwrap-3.8.4.25176 and winpack-3.8.4 and comfyj-2.10.25210.
We have reached to a point to blame the Hook since after disabling it the applications have no problem closing and no errors are being thrown.
We have also tried to disable Windows XP DEP completely by modifying the booot.ini, but that had no effect.
Is this some known issue? Is there some way to avoid this problem.
Any help and/or suggestion would be greatly appreciated.
Please let me know if I need to create a support ticket for this or if a complete test case is needed, etc.
Best regards,
Panayiotis Vlissidis
We are using the native Hook functionality of JNIWrapper/WinPACK and more specifically the Hook.CALLWNDPROC
in order to be able to communicate with other native applications by exchanging Window Handle messages.
We seem to have a problem though that some of these executables fail on close, with an error such as :
The instruction at "0x00b852e9" referenced memory at '0x00b900bb'. The memory could not be "read". Click on OK to terminate the program.
The problem seems to occur at Windows XP and Windows Server 2003 machines, while on Windows 7 and Windows Server 2008 the problem does not occur.
We are running under jre 1.7.0_09 (x32bit) and using jniwrap-3.8.4.25176 and winpack-3.8.4 and comfyj-2.10.25210.
We have reached to a point to blame the Hook since after disabling it the applications have no problem closing and no errors are being thrown.
We have also tried to disable Windows XP DEP completely by modifying the booot.ini, but that had no effect.
Is this some known issue? Is there some way to avoid this problem.
Any help and/or suggestion would be greatly appreciated.
Please let me know if I need to create a support ticket for this or if a complete test case is needed, etc.
Best regards,
Panayiotis Vlissidis
Reply all
Reply to author
Forward
0 new messages