Re: [rt.cpan.org #64575] Start callback not called with Strawberry Perl 5.10 / 5.12

Wed Jan 12 14:29:38 2011: Request 64575 was acted upon.
Transaction: Correspondence added by [email protected]
       Queue: Win32-Daemon
     Subject: Re: [rt.cpan.org #64575] Start callback not called with Strawberry Perl 5.10 / 5.12
   Broken in: (no value)
    Severity: (no value)
       Owner: Nobody
  Requestors: [email protected]
      Status: open
 Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=64575 >


> Yes, ALERT() will write to the log file, which isn't opened until you
> call Win32::Daemon::DebugOutputPath().  That's why I suggested you use
> 
> 	OutputDebugString( szBuffer );
> 
> The use the DebugView utility from Sysinternal (now part of Microsoft)
> to display all debugging output:
> 
>     http://technet.microsoft.com/en-us/sysinternals/bb896647

Ok, I tried it that way and inserted

OutputDebugStringA( "DllMain" );

in line 918 and

OutputDebugStringA( "Daemon::StartService: About to start the service
thread..." );

in line 1228.

In DebugView the second message appears, so receiving the messages work.
But the first message doesn't appear although it should be triggered
directly after entering DllMain().

I have to admit that it doesn't make sense - perhaps compiling with gcc
causes that by changing the signature in an invalid way!?
Do other perl modules use DllMain() for initializing?