Strange VM error

Hello,

I have a very strange error in a deployed application and can't
understand how to avoid it.

Dmitry Zamotkin


************************** Dolphin Virtual Machine Dump Report
***************************

19:21:16, 19.06.2006: SmallInteger does not understand
#callback:vfn:withArgumentsAt:

*----> VM Context <----*
Process: {089A0004:size 170 words, suspended frame 089A01D9, priority
5, callbacks 1
last failure 0:nil, FPE mask 3, thread nil}
Active Method: SessionManager>>logError:
IP: 017C8C99 (9)
SP: 089A038C
BP: 089A0360 (200)
ActiveFrame: {089A0364: cf 089A0345, sp 089A037C, bp 089A0360, ip 5,
BillingSessionManager(SessionManager)>>logError:}
        receiver: a BillingSessionManager
        arg[0]: a MessageNotUnderstood


New Method: VMLibrary>>dump:path:stackDepth:walkbackDepth:
Message Selector: dump:path:stackDepth:walkbackDepth:

*----> Stack Back Trace <----*
{089A0364: cf 089A0345, sp 089A037C, bp 089A0360, ip 5,
BillingSessionManager(SessionManager)>>logError:}
        receiver: a BillingSessionManager
        arg[0]: a MessageNotUnderstood

{089A0344: cf 089A0325, sp 089A0358, bp 089A0340, ip 3,
BillingSessionManager(SessionManager)>>unhandledException:}
        receiver: a BillingSessionManager
        arg[0]: a MessageNotUnderstood

{089A0324: cf 089A0305, sp 089A0338, bp 089A0320, ip 3,
BillingSessionManager(SessionManager)>>onUnhandledError:}
        receiver: a BillingSessionManager
        arg[0]: a MessageNotUnderstood

{089A0304: cf 089A02E9, sp 089A0318, bp 089A0304, ip 5,
MessageNotUnderstood(Error)>>defaultAction}
        receiver: a MessageNotUnderstood

{089A02E8: cf 089A02B5, sp 089A02FC, bp 089A02D0, ip 55,
MessageNotUnderstood(Exception)>>_propagateFrom:}
        receiver: a MessageNotUnderstood
        arg[0]: a ExceptionHandler
        stack temp[0]: nil
        stack temp[1]: a ExceptionHandler
        stack temp[2]: nil
        stack temp[3]: a Process('Main' base 089A0000 [ACTIVE] in
SessionManager>>logError: sp=00000000 ip=4 list=10060010)
        stack temp[4]: nil

{089A02B4: cf 089A0295, sp 089A02C8, bp 089A02B0, ip 6,
MessageNotUnderstood(Exception)>>_propagate}
        receiver: a MessageNotUnderstood
        stack temp[0]: nil

{089A0294: cf 089A0279, sp 089A02A8, bp 089A0294, ip 11,
MessageNotUnderstood(Exception)>>signal}
        receiver: a MessageNotUnderstood

{089A0278: cf 089A0255, sp 089A028C, bp 089A0270, ip 12,
MessageNotUnderstood class>>receiver:message:}
        receiver: MessageNotUnderstood
        arg[0]: 11
        arg[1]: Message selector: callback:vfn:withArgumentsAt: arguments: #(1
2 1233964 )

{089A0254: cf 089A0235, sp 089A0268, bp 089A0250, ip 4,
SmallInteger(Object)>>doesNotUnderstand:}
        receiver: 11
        arg[0]: Message selector: callback:vfn:withArgumentsAt: arguments: #(1
2 1233964 )

{089A0234: cf 089A0201, sp 089A0248, bp 089A0224, ip 22, [] in
ProcessorScheduler>>comCallback:id:subId:withArgumentsAt:cookie:}
        receiver: a ProcessorScheduler

{089A0200: cf 089A01D9, sp 089A0214, bp 089A01FC, ip 18,
BlockClosure>>ifCurtailed:}
        receiver: [] @ 0 in nil
        arg[0]: [] @ 31 in
ProcessorScheduler>>comCallback:id:subId:withArgumentsAt:cookie:

{089A01D8: cf 089A01A1, sp 089A01F4, bp 089A01C4, ip 35,
ProcessorScheduler>>comCallback:id:subId:withArgumentsAt:cookie:}
        receiver: a ProcessorScheduler
        arg[0]: 2
        arg[1]: 2
        arg[2]: 1
        arg[3]: 1233964
        arg[4]: 616874

{089A01A0: cf 089A0181, sp 089A01BC, bp 089A019C, ip 29,
InputState>>pumpMessage:}
        receiver: a InputState
        arg[0]: a MSG

{089A0180: cf 089A0155, sp 089A0194, bp 089A0170, ip 18,
InputState>>loopWhile:}
        receiver: a InputState
        arg[0]: [] @ 9 in InputState>>mainLoop
        stack temp[0]: a MSG
        stack temp[1]: true
        stack temp[2]: nil

{089A0154: cf 089A0139, sp 089A0168, bp 089A0154, ip 15,
InputState>>mainLoop}
        receiver: a InputState

{089A0138: cf 089A011D, sp 089A014C, bp 089A0138, ip 14, [] in
InputState>>forkMain}
        receiver: a InputState

{089A011C: cf 089A0101, sp 089A0130, bp 089A011C, ip 13,
ExceptionHandler(ExceptionHandlerAbstract)>>markAndTry}
        receiver: a ExceptionHandler

{089A0100: cf 089A00D9, sp 089A0114, bp 089A00FC, ip 22, [] in
ExceptionHandler(ExceptionHandlerAbstract)>>try:}
        receiver: a ExceptionHandler

{089A00D8: cf 089A00B9, sp 089A00EC, bp 089A00D4, ip 18,
BlockClosure>>ifCurtailed:}
        receiver: [] @ 0 in nil
        arg[0]: [] @ 39 in ExceptionHandlerAbstract>>try:

{089A00B8: cf 089A0095, sp 089A00CC, bp 089A00B0, ip 3,
BlockClosure>>ensure:}
        receiver: [] @ 17 in ExceptionHandlerAbstract>>try:
        arg[0]: [] @ 39 in ExceptionHandlerAbstract>>try:
        stack temp[0]: nil

{089A0094: cf 089A006D, sp 089A00A8, bp 089A0088, ip 44,
ExceptionHandler(ExceptionHandlerAbstract)>>try:}
        receiver: a ExceptionHandler
        arg[0]: [] @ 10 in InputState>>forkMain
        stack temp[0]: nil
        stack temp[1]: a Process('Main' base 089A0000 [ACTIVE] in
SessionManager>>logError: sp=00000000 ip=4 list=10060010)
        env temp[0]: nil

{089A006C: cf 089A0049, sp 089A0080, bp 089A0064, ip 7,
BlockClosure>>on:do:}
        receiver: [] @ 10 in InputState>>forkMain
        arg[0]: ProcessTermination
        arg[1]: [] @ 13 in BlockClosure>>newProcess

{089A0048: cf 00000001, sp 089A005C, bp 089A0048, ip 17, [] in
BlockClosure>>newProcess}
        receiver: [] @ 10 in InputState>>forkMain

<Bottom of stack>

***** End of dump *****

Dmitry,
"Dmitry Zamotkin" <[hidden email]> wrote in message
news:[hidden email]...
> Hello,
>
> I have a very strange error in a deployed application and can't
> understand how to avoid it.
>
> Dmitry Zamotkin
[...]
{089A0254: cf 089A0235, sp 089A0268, bp 089A0250, ip 4,
SmallInteger(Object)>>doesNotUnderstand:}
 receiver: 11
 arg[0]: Message selector: callback:vfn:withArgumentsAt: arguments: #(1
2 1233964 )
[...]
> {089A01D8: cf 089A01A1, sp 089A01F4, bp 089A01C4, ip 35,
> ProcessorScheduler>>comCallback:id:subId:withArgumentsAt:cookie:}
> receiver: a ProcessorScheduler
> arg[0]: 2
> arg[1]: 2
> arg[2]: 1
> arg[3]: 1233964
> arg[4]: 616874
[...]

I had a similar problem that resulted from COM objects having been cleaned
up too early.  For some possibly helpful ideas, check Blair's reply to my
post on Friday, April 14, 2006 5:04 PM.  It's also at this Google link:

http://groups.google.com/group/comp.lang.smalltalk.dolphin/browse_thread/thread/f21f40084cf4b917/02660c9fa1dbe3af?lnk=st&q=callback%3Avfn%3AwithArgumentsAt%3A+group%3Acomp.lang.smalltalk.dolphin&rnum=3&hl=en#02660c9fa1dbe3af

HTH,

Don