Occasionally I'm seeing the following sequence after which the image becomes
effectively frozen,
Assert fail @ 326 in ext\exCallC.c !oopIsImm(oArgumentKinds) &&
objClass(oArgumentKinds) == sysOop(byteArrayClassX)
Assert fail @ 327 in ext\exCallC.c !objHasPtrs(oArgumentKinds)
Assert fail @ 327 in ext\exCallC.c numArgs ==
(oopInt)(objByteDataSize(oArgumentKinds) - 1)
Assert fail @ 328 in ext\exCallC.c oopIsInt(oStructArgsSize)
Assert fail @ 329 in ext\exCallC.c oopIsInt(oStructReturnSize)
Assert fail @ 359 in ext\exCallC.c oopIsInt(oSpecifierFlags)
Now admittedly this happens while debugging somewhat complicated C
callbacks, but still curious what others may think about the exact cause.
Cheers!
-Boris
--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
[hidden email]
CONFIDENTIALITY NOTICE
This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.
Thank you.