[7.4] CCallbacks malfunction

> Hi,
>
> We are using a part of the COAST-Framework dealing with Windows service
> interface to start our application as a windows service. We load the
> package WinService and it worked well with Images before 7.4.
>
> Now I encounter the following problem:
>
> The method WinServiceInterface->startDispatcherWithHandler:serviceName:
> creates a CCallback -Object and passes it to a dipatchTable-Object which
> is then passed to Windows by StartServiceCtrlDispatcher. This function
> then calls the Ccallback-Block.
>
> And here is the problem: Obviously the call of the callback fails and
> Windows opens a requester with the text:
>
>       Fehlgeschlagene Anwendung visual.exe, Version 0.0.0.0,
>       fehlgeschlagenes Modul unknown, Version 0.0.0.0, Fehleradresse
>       0x00faaeb0.
>
> BUT: my Image is still responding, it doesn't fail. I used the
> target-function of the sysinternals process explorer to determine the
> process, which opened the dialog and it was….: csrcs.exe, the Client
> Server Runtime Process. After pressing one of the two buttons, my Image
> terminates.
>
> Very interesting:  The Fehleradresse 0x00faaeb0 is exactly the same
> value as the datum in the Ccallback-Object!
>
> After studying the CCallback-Class-Comments I think the virtual machine
> has a bug:
> Ccallback-Objects install a thunk in the heap to handle the callbacks of
> external code (like the Windows service API). Maybe this thunk is not
> working correctly.
>
> Has anybody experienced the same problems?
>
> Greetings
>
> Klaus Mülheims
>
> Collogia AG
> Ubierring 11
>  
> 50678 Köln
> Germany
> +49 221 336080
> _http://www.collogia.de_
>
> ------------------------------------------------------------------------
> Diese Nachricht ist vertraulich. Wenn Sie nicht der beabsichtigte
> Empfänger sind, informieren Sie bitte den Absender. Das unbefugte
> Kopieren oder Weiterleiten ist nicht gestattet. Wegen der
> Manipulierbarkeit von E-Mails übernehmen wir keine Haftung für den Inhalt.
>

> Hi,
>
> We are using a part of the COAST-Framework dealing with Windows service
> interface to start our application as a windows service. We load the
> package WinService and it worked well with Images before 7.4.
>
> Now I encounter the following problem:
>
> The method WinServiceInterface->startDispatcherWithHandler:serviceName:
> creates a CCallback -Object and passes it to a dipatchTable-Object which
> is then passed to Windows by StartServiceCtrlDispatcher. This function
> then calls the Ccallback-Block.
>
> And here is the problem: Obviously the call of the callback fails and
> Windows opens a requester with the text:
>
>       Fehlgeschlagene Anwendung visual.exe, Version 0.0.0.0,
>       fehlgeschlagenes Modul unknown, Version 0.0.0.0, Fehleradresse
>       0x00faaeb0.
>
> BUT: my Image is still responding, it doesn't fail. I used the
> target-function of the sysinternals process explorer to determine the
> process, which opened the dialog and it was….: csrcs.exe, the Client
> Server Runtime Process. After pressing one of the two buttons, my Image
> terminates.
>
> Very interesting:  The Fehleradresse 0x00faaeb0 is exactly the same
> value as the datum in the Ccallback-Object!
>
> After studying the CCallback-Class-Comments I think the virtual machine
> has a bug:
> Ccallback-Objects install a thunk in the heap to handle the callbacks of
> external code (like the Windows service API). Maybe this thunk is not
> working correctly.
>
> Has anybody experienced the same problems?
>
> Greetings
>
> Klaus Mülheims
>
> Collogia AG
> Ubierring 11
>  
> 50678 Köln
> Germany
> +49 221 336080
> _http://www.collogia.de_
>
> ------------------------------------------------------------------------
> Diese Nachricht ist vertraulich. Wenn Sie nicht der beabsichtigte
> Empfänger sind, informieren Sie bitte den Absender. Das unbefugte
> Kopieren oder Weiterleiten ist nicht gestattet. Wegen der
> Manipulierbarkeit von E-Mails übernehmen wir keine Haftung für den Inhalt.
>

> Hi,
>
> We are using a part of the COAST-Framework dealing with Windows service
> interface to start our application as a windows service. We load the
> package WinService and it worked well with Images before 7.4.
>
> Now I encounter the following problem:
>
> The method WinServiceInterface->startDispatcherWithHandler:serviceName:
> creates a CCallback -Object and passes it to a dipatchTable-Object which
> is then passed to Windows by StartServiceCtrlDispatcher. This function
> then calls the Ccallback-Block.
>
> And here is the problem: Obviously the call of the callback fails and
> Windows opens a requester with the text:
>
>       Fehlgeschlagene Anwendung visual.exe, Version 0.0.0.0,
>       fehlgeschlagenes Modul unknown, Version 0.0.0.0, Fehleradresse
>       0x00faaeb0.
>
> BUT: my Image is still responding, it doesn't fail. I used the
> target-function of the sysinternals process explorer to determine the
> process, which opened the dialog and it was….: csrcs.exe, the Client
> Server Runtime Process. After pressing one of the two buttons, my Image
> terminates.
>
> Very interesting:  The Fehleradresse 0x00faaeb0 is exactly the same
> value as the datum in the Ccallback-Object!
>
> After studying the CCallback-Class-Comments I think the virtual machine
> has a bug:
> Ccallback-Objects install a thunk in the heap to handle the callbacks of
> external code (like the Windows service API). Maybe this thunk is not
> working correctly.
>
> Has anybody experienced the same problems?
>
> Greetings
>
> Klaus Mülheims
>
> Collogia AG
> Ubierring 11
>  
> 50678 Köln
> Germany
> +49 221 336080
> _http://www.collogia.de_
>
> ------------------------------------------------------------------------
> Diese Nachricht ist vertraulich. Wenn Sie nicht der beabsichtigte
> Empfänger sind, informieren Sie bitte den Absender. Das unbefugte
> Kopieren oder Weiterleiten ist nicht gestattet. Wegen der
> Manipulierbarkeit von E-Mails übernehmen wir keine Haftung für den Inhalt.
>

>Greetings
>
>Klaus Mülheims
>
>
>Collogia AG
>Ubierring 11
>
>50678 Köln
>Germany
>+49 221 336080
>http://www.collogia.de
>
>-----Ursprüngliche Nachricht-----
>Von: Mülheims, Klaus [mailto:[hidden email]]
>Gesendet: Montag, 6. März 2006 16:50
>An: Christian Schuckmann; [hidden email]
>Betreff: AW: [7.4] CCallbacks malfunction
>
>Hi Christian,
>
>Thanks for this very quick response. I tried the new version, but... Exactly the same error.
>Any other ideas?
>
>Greetings
>
>Klaus Mülheims
>
>
>Collogia AG
>Ubierring 11
>
>50678 Köln
>Germany
>+49 221 336080
>http://www.collogia.de
>
>-----Ursprüngliche Nachricht-----
>Von: Christian Schuckmann [mailto:[hidden email]]
>Gesendet: Montag, 6. März 2006 16:19
>An: [hidden email]
>Betreff: Re: [7.4] CCallbacks malfunction
>
>Ho,
>
>which version of the WinServiceInterface do you use?
>There is an old one - part of COAST and a new one, we
>published to the public repository last year.
>With the new one we did not yet encounter any problems -
>at least it seems to work under 7.4 at a first glance.
>
>-Christian
>
>Mülheims wrote:
>> Hi,
>>
>> We are using a part of the COAST-Framework dealing with Windows service
>> interface to start our application as a windows service. We load the
>> package WinService and it worked well with Images before 7.4.
>>
>> Now I encounter the following problem:
>>
>> The method WinServiceInterface->startDispatcherWithHandler:serviceName:
>> creates a CCallback -Object and passes it to a dipatchTable-Object which
>> is then passed to Windows by StartServiceCtrlDispatcher. This function
>> then calls the Ccallback-Block.
>>
>> And here is the problem: Obviously the call of the callback fails and
>> Windows opens a requester with the text:
>>
>>       Fehlgeschlagene Anwendung visual.exe, Version 0.0.0.0,
>>       fehlgeschlagenes Modul unknown, Version 0.0.0.0, Fehleradresse
>>       0x00faaeb0.
>>
>> BUT: my Image is still responding, it doesn't fail. I used the
>> target-function of the sysinternals process explorer to determine the
>> process, which opened the dialog and it was….: csrcs.exe, the Client
>> Server Runtime Process. After pressing one of the two buttons, my Image
>> terminates.
>>
>> Very interesting:  The Fehleradresse 0x00faaeb0 is exactly the same
>> value as the datum in the Ccallback-Object!
>>
>> After studying the CCallback-Class-Comments I think the virtual machine
>> has a bug:
>> Ccallback-Objects install a thunk in the heap to handle the callbacks of
>> external code (like the Windows service API). Maybe this thunk is not
>> working correctly.
>>
>> Has anybody experienced the same problems?
>>
>> Greetings
>>
>> Klaus Mülheims
>>
>> Collogia AG
>> Ubierring 11
>>  
>> 50678 Köln
>> Germany
>> +49 221 336080
>> _http://www.collogia.de_
>>
>> ------------------------------------------------------------------------
>> Diese Nachricht ist vertraulich. Wenn Sie nicht der beabsichtigte
>> Empfänger sind, informieren Sie bitte den Absender. Das unbefugte
>> Kopieren oder Weiterleiten ist nicht gestattet. Wegen der
>> Manipulierbarkeit von E-Mails übernehmen wir keine Haftung für den Inhalt.
>>
>
>
>--
>Christian Schuckmann                           intelligent views gmbh
>Development Manager Core Technologies          Julius-Reiber-Str. 17
>Tel/Fax ++49 6151 5006 - 240/138               64293 Darmstadt
>e-mail: [hidden email]                http://www.i-views.de/
>
>
>
>Diese Nachricht ist vertraulich. Wenn Sie nicht der beabsichtigte Empfänger sind, informieren Sie bitte den Absender. Das unbefugte Kopieren oder Weiterleiten ist nicht gestattet. Wegen der Manipulierbarkeit von E-Mails übernehmen wir keine Haftung für den Inhalt.
>
>
>Diese Nachricht ist vertraulich. Wenn Sie nicht der beabsichtigte Empfänger sind, informieren Sie bitte den Absender. Das unbefugte Kopieren oder Weiterleiten ist nicht gestattet. Wegen der Manipulierbarkeit von E-Mails übernehmen wir keine Haftung für den Inhalt.

>Greetings
>
>Klaus Mülheims
>
>
>Collogia AG
>Ubierring 11
>
>50678 Köln
>Germany
>+49 221 336080
>http://www.collogia.de
>
>-----Ursprüngliche Nachricht-----
>Von: Mülheims, Klaus [mailto:[hidden email]]
>Gesendet: Montag, 6. März 2006 16:50
>An: Christian Schuckmann; [hidden email]
>Betreff: AW: [7.4] CCallbacks malfunction
>
>Hi Christian,
>
>Thanks for this very quick response. I tried the new version, but... Exactly the same error.
>Any other ideas?
>
>Greetings
>
>Klaus Mülheims
>
>
>Collogia AG
>Ubierring 11
>
>50678 Köln
>Germany
>+49 221 336080
>http://www.collogia.de
>
>-----Ursprüngliche Nachricht-----
>Von: Christian Schuckmann [mailto:[hidden email]]
>Gesendet: Montag, 6. März 2006 16:19
>An: [hidden email]
>Betreff: Re: [7.4] CCallbacks malfunction
>
>Ho,
>
>which version of the WinServiceInterface do you use?
>There is an old one - part of COAST and a new one, we
>published to the public repository last year.
>With the new one we did not yet encounter any problems -
>at least it seems to work under 7.4 at a first glance.
>
>-Christian
>
>Mülheims wrote:
>> Hi,
>>
>> We are using a part of the COAST-Framework dealing with Windows service
>> interface to start our application as a windows service. We load the
>> package WinService and it worked well with Images before 7.4.
>>
>> Now I encounter the following problem:
>>
>> The method WinServiceInterface->startDispatcherWithHandler:serviceName:
>> creates a CCallback -Object and passes it to a dipatchTable-Object which
>> is then passed to Windows by StartServiceCtrlDispatcher. This function
>> then calls the Ccallback-Block.
>>
>> And here is the problem: Obviously the call of the callback fails and
>> Windows opens a requester with the text:
>>
>>       Fehlgeschlagene Anwendung visual.exe, Version 0.0.0.0,
>>       fehlgeschlagenes Modul unknown, Version 0.0.0.0, Fehleradresse
>>       0x00faaeb0.
>>
>> BUT: my Image is still responding, it doesn't fail. I used the
>> target-function of the sysinternals process explorer to determine the
>> process, which opened the dialog and it was....: csrcs.exe, the Client
>> Server Runtime Process. After pressing one of the two buttons, my Image
>> terminates.
>>
>> Very interesting:  The Fehleradresse 0x00faaeb0 is exactly the same
>> value as the datum in the Ccallback-Object!
>>
>> After studying the CCallback-Class-Comments I think the virtual machine
>> has a bug:
>> Ccallback-Objects install a thunk in the heap to handle the callbacks of
>> external code (like the Windows service API). Maybe this thunk is not
>> working correctly.
>>
>> Has anybody experienced the same problems?
>>
>> Greetings
>>
>> Klaus Mülheims
>>
>> Collogia AG
>> Ubierring 11
>>  
>> 50678 Köln
>> Germany
>> +49 221 336080
>> _http://www.collogia.de_
>>
>> ------------------------------------------------------------------------
>> Diese Nachricht ist vertraulich. Wenn Sie nicht der beabsichtigte
>> Empfänger sind, informieren Sie bitte den Absender. Das unbefugte
>> Kopieren oder Weiterleiten ist nicht gestattet. Wegen der
>> Manipulierbarkeit von E-Mails übernehmen wir keine Haftung für den Inhalt.
>>
>
>
>--
>Christian Schuckmann                           intelligent views gmbh
>Development Manager Core Technologies          Julius-Reiber-Str. 17
>Tel/Fax ++49 6151 5006 - 240/138               64293 Darmstadt
>e-mail: [hidden email]                http://www.i-views.de/
>
>
>
>Diese Nachricht ist vertraulich. Wenn Sie nicht der beabsichtigte Empfänger sind, informieren Sie bitte den Absender. Das unbefugte Kopieren oder Weiterleiten ist nicht gestattet. Wegen der Manipulierbarkeit von E-Mails übernehmen wir keine Haftung für den Inhalt.
>
>
>Diese Nachricht ist vertraulich. Wenn Sie nicht der beabsichtigte Empfänger sind, informieren Sie bitte den Absender. Das unbefugte Kopieren oder Weiterleiten ist nicht gestattet. Wegen der Manipulierbarkeit von E-Mails übernehmen wir keine Haftung für den Inhalt.