Dolphin 5.1.4 crashes under Windows 2003

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Dolphin 5.1.4 crashes under Windows 2003

Theo Pronk
The server is an HP ProLiant ML110G2, running Win2003 Standard Edition
SP1.
Dual Process or Pentium 4 3Ghz Family 15 Model 4 Stepping 1.

The problem occurs as soon as the application is started.
It run fine on Win2000 Server or Desktop PC running XP.

The dump points to a GPFault that looks like something to do with the
userlibrary but I'm not sure. Can anyone help?

Cheers, Theo Pronk

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

12:02:06 PM, 11/28/2005: Invalid access to memory location. Writing
0x6DFCFDC, IP 0x6DFCFDC ()

*----> VM Context <----*
Process: {06F30004:size 170 words, suspended frame 06F301E1, priority
5, callbacks 0
last failure 2:nil, FPE mask 3, thread nil}
Active Method: SessionManager>>logError:
IP: 06CED46D (13)
SP: 06F30358
BP: 06F30330 (187)
ActiveFrame: {06F30334: cf 06F30319, sp 06F30348, bp 06F30330, ip 5,
SASdownloadManagerSession(SessionManager)>>logError:}
        receiver: a SASdownloadManagerSession
        arg[0]: a GPFault


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

*----> Stack Back Trace <----*
{06F30334: cf 06F30319, sp 06F30348, bp 06F30330, ip 5,
SASdownloadManagerSession(SessionManager)>>logError:}
        receiver: a SASdownloadManagerSession
        arg[0]: a GPFault

{06F30318: cf 06F302FD, sp 06F30328, bp 06F30314, ip 4,
SASdownloadManagerSession(SessionManager)>>unhandledException:}
        receiver: a SASdownloadManagerSession
        arg[0]: a GPFault

{06F302FC: cf 06F302E1, sp 06F3030C, bp 06F302F8, ip 4,
SASdownloadManagerSession(SessionManager)>>onUnhandledError:}
        receiver: a SASdownloadManagerSession
        arg[0]: a GPFault

{06F302E0: cf 06F302C9, sp 06F302F0, bp 06F302E0, ip 5,
GPFault(Error)>>defaultAction}
        receiver: a GPFault

{06F302C8: cf 06F302B5, sp 06F302D8, bp 06DFD630, ip 57,
GPFault(Exception)>>_propagateFrom:}
        receiver: a GPFault
        arg[0]: a ExceptionHandler
        temp[0]: nil
        temp[1]: a ExceptionHandler
        temp[2]: nil
        temp[3]: a Process(InputState>>forkMain base 06F30000 [ACTIVE] in
SessionManager>>logError: sp=00000000 ip=8 list=nil)
        temp[4]: nil

{06F302B4: cf 06F30299, sp 06F302C4, bp 06F302B0, ip 6,
GPFault(Exception)>>_propagate}
        receiver: a GPFault
        temp[0]: nil

{06F30298: cf 06F30281, sp 06F302A8, bp 06F30298, ip 12,
GPFault(Exception)>>signal}
        receiver: a GPFault

{06F30280: cf 06F30261, sp 06F30290, bp 06F30278, ip 8, GPFault
class(Win32Fault class)>>signal:with:}
        receiver: GPFault
        arg[0]: nil
        arg[1]: a EXCEPTION_RECORD

{06F30260: cf 06F30245, sp 06F30270, bp 06F3025C, ip 5, GPFault
class(Exception class)>>signalWith:}
        receiver: GPFault
        arg[0]: a EXCEPTION_RECORD

{06F30244: cf 06F30225, sp 06F30254, bp 06F3023C, ip 11,
ProcessorScheduler>>gpFault:}
        receiver: a ProcessorScheduler
        arg[0]: a ByteArray
        temp[0]: a EXCEPTION_RECORD

{06F30224: cf 06F30209, sp 06F30234, bp 06DFD710, ip 11, [] in
ProcessorScheduler>>vmi:list:no:with:}
        receiver: a ProcessorScheduler
        arg[0]: 476
        arg[1]: nil
        arg[2]: 5
        arg[3]: a ByteArray

{06F30208: cf 06F301F5, sp 06F30220, bp 06DFD668, ip 17,
BlockClosure>>ifCurtailed:}
        receiver: [] @ 6094854 in nil
        arg[0]: [] @ 16 in ProcessorScheduler>>vmi:list:no:with:
        temp[0]: nil
        temp[1]: nil
        temp[2]: nil

{06F301F4: cf 06F301E1, sp 06F30204, bp 06DFD710, ip 20,
ProcessorScheduler>>vmi:list:no:with:}
        receiver: a ProcessorScheduler
        arg[0]: 476
        arg[1]: nil
        arg[2]: 5
        arg[3]: a ByteArray

{06F301E0: cf 06F301AD, sp 06F301F0, bp 06F301C4, ip 1,
UserLibrary(ExternalLibrary)>>invalidCall}
        receiver: a UserLibrary
        temp[0]: nil
        temp[1]: nil
        temp[2]: nil
        temp[3]: nil
        temp[4]: nil
        temp[5]: nil
        temp[6]: nil

{06F301AC: cf 06F3018D, sp 06F301BC, bp 06F301A4, ip 3,
UserLibrary>>enumWindows:lParam:}
        receiver: a UserLibrary
        arg[0]: a ByteArray
        arg[1]: 0

{06F3018C: cf 06F30179, sp 06F3019C, bp 06DFD6A0, ip 21,
InputState>>topLevelHandlesDo:}
        receiver: a InputState
        arg[0]: [] @ 6 in InputState>>uiIdle
        temp[0]: a BlockCallback
        temp[1]: nil
        temp[2]: nil
        temp[3]: nil

{06F30178: cf 06F30165, sp 06F30188, bp 06DFD6D8, ip 23,
InputState>>uiIdle}
        receiver: a InputState
        temp[0]: nil

{06F30164: cf 06F3014D, sp 06F30174, bp 06F30164, ip 3,
InputState>>aboutToIdle}
        receiver: a InputState

{06F3014C: cf 06F30131, sp 06F3015C, bp 06F30148, ip 5,
InputState>>waitForInput:}
        receiver: a InputState
        arg[0]: true

{06F30130: cf 06F30109, sp 06F30140, bp 06F30120, ip 34,
InputState>>loopWhile:}
        receiver: a InputState
        arg[0]: [] @ 6 in InputState>>mainLoop
        temp[0]: a MSG
        temp[1]: true
        temp[2]: nil

{06F30108: cf 06F300F5, sp 06F30118, bp 06DFD860, ip 12,
InputState>>mainLoop}
        receiver: a InputState

{06F300F4: cf 06F300E1, sp 06F30104, bp 06DFDA58, ip 13, [] in
InputState>>forkMain}
        receiver: a InputState

{06F300E0: cf 06F300CD, sp 06F300F0, bp 06DFD7F0, ip 11,
ExceptionHandler(ExceptionHandlerAbstract)>>markAndTry}
        receiver: a ExceptionHandler
        temp[0]: nil

{06F300CC: cf 06F300B1, sp 06F300DC, bp 06DFD978, ip 21, [] in
ExceptionHandler(ExceptionHandlerAbstract)>>try:}
        receiver: a ExceptionHandler
        arg[0]: [] @ 8 in InputState>>forkMain
        temp[0]: nil
        temp[1]: nil
        temp[2]: a Process(InputState>>forkMain base 06F30000 [ACTIVE] in
SessionManager>>logError: sp=00000000 ip=8 list=nil)

{06F300B0: cf 06F3009D, sp 06F300C8, bp 06DFD908, ip 17,
BlockClosure>>ifCurtailed:}
        receiver: [] @ 6094854 in nil
        arg[0]: [] @ 34 in ExceptionHandlerAbstract>>try:
        temp[0]: nil
        temp[1]: nil
        temp[2]: nil

{06F3009C: cf 06F3007D, sp 06F300AC, bp 06F30094, ip 4,
BlockClosure>>ensure:}
        receiver: [] @ 15 in ExceptionHandlerAbstract>>try:
        arg[0]: [] @ 34 in ExceptionHandlerAbstract>>try:
        temp[0]: nil

{06F3007C: cf 06F30069, sp 06F3008C, bp 06DFD978, ip 39,
ExceptionHandler(ExceptionHandlerAbstract)>>try:}
        receiver: a ExceptionHandler
        arg[0]: [] @ 8 in InputState>>forkMain
        temp[0]: nil
        temp[1]: nil
        temp[2]: a Process(InputState>>forkMain base 06F30000 [ACTIVE] in
SessionManager>>logError: sp=00000000 ip=8 list=nil)

{06F30068: cf 06F30049, sp 06F30078, bp 06F30060, ip 7,
BlockClosure>>on:do:}
        receiver: [] @ 8 in InputState>>forkMain
        arg[0]: ProcessTermination
        arg[1]: [] @ 12 in BlockClosure>>newProcess

{06F30048: cf 00000001, sp 06F30058, bp 06DFD9B0, ip 17, [] in
BlockClosure>>newProcess}
        receiver: [] @ 8 in InputState>>forkMain
        temp[0]: nil

<Bottom of stack>

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


Reply | Threaded
Open this post in threaded view
|

Re: Dolphin 5.1.4 crashes under Windows 2003

Theo Pronk
Firstly, its here twice because I hit the button twice.

Secondly, I've also discovered (like everyone else) that Ghoul is
fantastic - thanks Chris.

According to Ghoul the error is a promitive failure when calling:

   UserLibrary>>enumWindows: lParam:
      after
   InputState>>topLevelHandlesDo:

Does this mean that the parameters to UserLibary are somehow different
of 2003 server? And what can I do to get it working (note: this is part
of a business app. to be put into production very soon - all testing
was done on windows 2000 server).

Any help would be appriciated.
Cheers, Theo


Reply | Threaded
Open this post in threaded view
|

Re: Dolphin 5.1.4 crashes under Windows 2003

Schwab,Wilhelm K
Theo,

> Firstly, its here twice because I hit the button twice.
>
> Secondly, I've also discovered (like everyone else) that Ghoul is
> fantastic - thanks Chris.
>
> According to Ghoul the error is a promitive failure when calling:
>
>    UserLibrary>>enumWindows: lParam:
>       after
>    InputState>>topLevelHandlesDo:
>
> Does this mean that the parameters to UserLibary are somehow different
> of 2003 server? And what can I do to get it working (note: this is part
> of a business app. to be put into production very soon - all testing
> was done on windows 2000 server).

EnumWindows() is mentioned sufficiently often that I hang my head in
sham for not recalling what problems in calling it mean in a situation
like this ;)

Check Ian's archives, because an answer might be forthcoming.

Have a good one,

Bill


--
Wilhelm K. Schwab, Ph.D.
[hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: Dolphin 5.1.4 crashes under Windows 2003

Andy Bower-3
In reply to this post by Theo Pronk
Theo,

> According to Ghoul the error is a promitive failure when calling:
>
>    UserLibrary>>enumWindows: lParam:
>       after
>    InputState>>topLevelHandlesDo:
>
> Does this mean that the parameters to UserLibary are somehow different
> of 2003 server? And what can I do to get it working (note: this is
> part of a business app. to be put into production very soon - all
> testing was done on windows 2000 server).

There is a thread started on 11th Nov "Deployed App crashing on Server
2003" which seems to show a similar problem. Take a look at the posts
there to see if any help.

 From your original post it isn't clear whether your application is a
console or a GUI app. Also are you running under a 64bit version of
Windows? Stefan's app was a console application and the problem
occurred at termination. From what you say, your app fails at startup
is that right?

Best regards,

--
Andy Bower
Dolphin Support
www.object-arts.com