| || |
Silk fails generating exception
I just started playing with Silk and its record features while learning 4Test and trying to generate some real testcase to
test my application.
This application is pretty large with
several daemons running in background
that makes my machine fairly slower.
I'm not sure if because of the application daemons or something else, sometimes the
agent loses communication with Silk test
(it might be).
But yesterday I ran into a weird situation
where the application crashed and so did
Since then, Silk is no longer able to load, failing miserably with an
"unhandled exception in partner.exe
"The instruction at 0x004e032a referenced
memory at 0xfffffffc. The memory could not
I already removed Silk and reinstalled it
again but didn't solve the problem.
I keep thinking that removing and reinstalling the application should not be
the solution but it might worth a try.
What else could I do ?
Is it a known problem ?
Is there a patch to correct it ?
* In time, I'm using 5.0, Windows NT server 4.0 and Service pack 5 applied.
Thanks in advance,
Alex De Lara.
Sw. Test Engineer
Re: Silk fails generating exception
I have found the cause of this...
>> "unhandled exception in partner.exe
>> "The instruction at 0x004e032a referenced
>> memory at 0xfffffffc. The memory could not
>> be written."
When SilkTest starts it compiles all files,
including the ones I specified in "Option -> Runtime -> Use Files..."
It happened that I had modified my inc file
and inserted an error.
Here is the smallest file I could produce
that makes Silk to crash:
[ ] const wMainWindow = outerWin
[-] window MainWin outerWin
[-] multitag "outerX"
[ ] "X"
[-] childWin FoundObject
[-] multitag "Found Object"
[ ] "#1"
[ ] // !!! ERROR : NEXT LINE CAUSE PARTNER TO TRAP
[ ] parent outerWin
This trap is not supposed to happen and the the compiler should point to the erro instead of trapping