Forum Discussion
hlalumiere
14 years agoRegular Contributor
Ok so I followed your instructions, however even your report generator doesn't seem to work. I can have it open my app no problem, it keeps on tracing although seriously slowing the application down. I can also open TC9 with another instance, everything is fine there. The problem occurs when actually starting the test run. TestComplete never finds my application's process, and it hangs there doing nothing at all. I was able to export the TestComplete part of the report, which I have attached, but the report generator for my app's instance refuses to save the report when I click Generate. I see all the info on screen however, so I will try to spit it out here, omitting the useless Thread ID lines.
The problem seems to arise when the tcVbHook.dll file is loaded. The log shows all the other "Hook" libraries loading fine, like this:
A module is loaded | C:\...\tcIEHook.dll | Base address: 0x10FD0000 | File size: 1969232 byte(s)
It's the same for tcHook.dll, aqComm.dll, tcOpenAppHook.dll, tcMSAAAppHook.dll, aqComHelp.dll, tcDelphiHook.dll, etc... Even tcVbHook.dll initially seems to load fine. But then immediately after tcAgHook.dll is loaded and its threads started:
First chance exception 0xC0000005 ACCESS_VIOLATION occured at 0x7487D09C, read of address 0x5C3A4322 at 0x7487D09C (in C:\Windows\SysWOW64\kernel32.dll)
Then what looks like a stack trace:
0x7487D09C in kernel32.dll
0x0D88A012 in tcVBHook.dll
0x0D88A342 in tcVBHook.dll
0x0D8938A7 in tcVBHook.dll
0x0D893AB7 in tcVBHook.dll
0x0D87EA72 in tcVBHook.dll
0x0D87F2C5 in tcVBHook.dll
0x0D87EA28 in tcVBHook.dll
0x756D8336 in user32.dll
0x756C80A9 in user32.dll
0x756C8BA1 in user32.dll
0x7710010A in ntdll.dll
0x7294A698 in msvbvm60.dll
0x7294A63F in msvbvm60.dll
0x7294A51D in msvbvm60.dll
0x7294A4E8 in msvbvm60.dll
0x72943644 in msvbvm60.dll
0x005F8066 in Dynacom.exe <-- This is my app.
0x77129EF2 in ntdll.dll
0x77129EC5 in ntdll.dll
Then this repeats in an infinite loop from the exception. So I am unable to trace the issue mentionned earlier, but maybe this has to do with it. Or maybe not.
The problem seems to arise when the tcVbHook.dll file is loaded. The log shows all the other "Hook" libraries loading fine, like this:
A module is loaded | C:\...\tcIEHook.dll | Base address: 0x10FD0000 | File size: 1969232 byte(s)
It's the same for tcHook.dll, aqComm.dll, tcOpenAppHook.dll, tcMSAAAppHook.dll, aqComHelp.dll, tcDelphiHook.dll, etc... Even tcVbHook.dll initially seems to load fine. But then immediately after tcAgHook.dll is loaded and its threads started:
First chance exception 0xC0000005 ACCESS_VIOLATION occured at 0x7487D09C, read of address 0x5C3A4322 at 0x7487D09C (in C:\Windows\SysWOW64\kernel32.dll)
Then what looks like a stack trace:
0x7487D09C in kernel32.dll
0x0D88A012 in tcVBHook.dll
0x0D88A342 in tcVBHook.dll
0x0D8938A7 in tcVBHook.dll
0x0D893AB7 in tcVBHook.dll
0x0D87EA72 in tcVBHook.dll
0x0D87F2C5 in tcVBHook.dll
0x0D87EA28 in tcVBHook.dll
0x756D8336 in user32.dll
0x756C80A9 in user32.dll
0x756C8BA1 in user32.dll
0x7710010A in ntdll.dll
0x7294A698 in msvbvm60.dll
0x7294A63F in msvbvm60.dll
0x7294A51D in msvbvm60.dll
0x7294A4E8 in msvbvm60.dll
0x72943644 in msvbvm60.dll
0x005F8066 in Dynacom.exe <-- This is my app.
0x77129EF2 in ntdll.dll
0x77129EC5 in ntdll.dll
Then this repeats in an infinite loop from the exception. So I am unable to trace the issue mentionned earlier, but maybe this has to do with it. Or maybe not.