Reinhard Pagitsch said:
Peter said:
Reinhard Pagitsch said:
Every time I try to shutdown or log off, pop-up is comming up with
"application doesn't response" and expecting to kill by clicking a
button -> very dirty thing :-/
So, I tried to catch WM_QUERYENDSESSION (using Win32::GUI::Hook), but no
You should reveive a WM_CLOSE according to Bill.
not really, I'm affraid windows doesn't sent neither WM_CLOSE nor
WM_QUIT because of the same reason of not sending WM_QUERYENDSESSION.
Have you also read the MSDN documentation about SetConsoleCtrlHandler?
The last paragraph say:
The system generates CTRL_CLOSE_EVENT, CTRL_LOGOFF_EVENT, and
CTRL_SHUTDOWN_EVENT signals when the user closes the console, logs off,
or shuts down the system so that the process has an opportunity to clean
up before termination. Console functions, or any C run-time functions
that call console functions, may not work reliably during processing of
any of the three signals mentioned previously. The reason is that some
or all of the internal console cleanup routines may have been called
before executing the process signal handler.
this is the thing I wanted to do but the Win32::API::Callback doesn't
work :-(
But I have a small workaround for now, I wrote a C module where I
register a C-written-callback where I run ExitProcess().
It's dirty to me, because I have no possibility to clean up or do
something else, but, the process really ends on logoff.
Neverthereless, I still interesting in Win32::API::Callback to get it
work, because it would be very useful feature in Win32 enviroment.
I tried to write something similars, but how I mentioned above, I've a
problem to call a perl routine from the C-callback, not even the
simplest one from perlcall manpage worked, I got SEGFAULT every time.
I'm not sure, but could it be a problem calling the call_pv() or call_sv()
from the callback which is launching in another thread ?
[...]
Can you send me the code you are using, maybe I can find it out why the
Win32::API::Callback Module crashes.
just a simple define of a callback:
----snip---
use Win32::API;
use Win32::API::Callback;
my $callback = Win32::API::Callback->new(
sub { my($a, $b) = @_; return $a+$b; },
"NN", "N",
);
----snap---
gives the SEGFAULT and following message written to the console:
"Free to wrong pool 15e2660 not e58b2660, <DATA> line 164."
As Thomas wrote, the Module is broken. I assume to remove it and install
it again. In my environment, Activestate 5.8.8 on XP Sp2, this code
works perfect.
You can download it from
http://www.bribes.org/perl/ppm/ (30-Jan-2007)
or Activestate.
Here you can find a list of PPM repositories:
http://win32.perl.org/wiki/index.php?title=PPM_Repositories
thanks for the link !
Module doesn't crash anymore
now I only one step further, but the call I wanted to do fails now
in calling the callback, here the code:
------------------------snip-----------------
use strict;
use Win32::API;
use Win32::API::Callback;
sub handler {
my $type = shift;
print "RECEIVED SIGNAL: $type\n",;
return 1;
}
my $callback =
Win32::API::Callback->new(\&handler, "I", "I" );
my $function =
Win32::API->new('kernel32','SetConsoleCtrlHandler','KI','I');
$function->Call($callback,1);
my $i= 0;
while ($i<2000) {
print ++$i,"\n";
sleep(1); # in this loop press Ctrl+C
}
-----------------------snap----------------------
it crashs now not by defining the callback but
after I press "Ctrl+C" inside the loop :-/
If I do this in XSUB it seems to work, but only to do ExitProcess(),
But I'd like to be able to call a callback.
For comparison here comes my working XS code (with ExitProcess()):
-----------snip------------------
#include "EXTERN.h"
#include "perl.h"
#include "XSUB.h"
#include "ppport.h"
#include "windows.h"
#include "wincon.h"
#define MAX_EVENT CTRL_SHUTDOWN_EVENT
int event[7] = { 0,0,0,0,0,0,0 };
BOOL WINAPI CtrlHandler(DWORD type) {
printf("received: %d\n",type);
if (type > MAX_EVENT)
return FALSE;
if (event[type])
ExitProcess(0);
return FALSE;
}
MODULE = Logoff PACKAGE = Logoff
int
LogoffOnEvent(ev, logoff)
int ev
int logoff
CODE:
int rv;
if (ev > MAX_EVENT) {
rv = -1;
} else {
event[ev] = logoff;
rv = SetConsoleCtrlHandler(CtrlHandler,TRUE);
}
RETVAL = rv;
OUTPUT:
RETVAL
-----------snap------------------
to test this module I use this simple piece of perl code:
-----------snip-----------------
use Logoff;
Logoff::LogoffOnEvent(5,1); # quits after Logoff
Logoff::LogoffOnEvent(0,1); # quits after Ctrl+C
do {
print "sleeping...$i\n"; # try to logoff or Ctrl+C
sleep(1);
} until $i > 10000;
------------snap----------------
the big disadvantage of this is that I have no possibility to clean up
my perl code.
As I wrote before, I tried already to call a perl callback in
CtrlHandler using call_sv() or call_pv(), without any success,
this ends every time with segfault calling the perl code,
the same thing as the perl variant using Win32::API::Callback
also does (ofcourse after I re-installed the Win32::API-0.46
module from
http://www.bribes.org/perl/ppm/).
Are there a more restrictions inside a CtrlHandler which disallow to
do something like call a perl callback ?
regards
Peter
