Hi,
Olivier Mengué schrieb:
> So here is my question: what can I use to track what is keeping the session
> alive ? How can I inspect the session (even using private APIs) and the
> kernel ?
Adding following line to the top of your code, before you create the
session will output additional kerne
Hi,
I'm using POE::Wheel::Run::Win32 0.16 with POE 1.006 on ActivePerl 5.10
(1003).
My POE-based program has a main session which launchs sessions which use a
P::W::R::Win32 to run an external process.
The process are running OK, the output is returned OK, the sig_child is
fired as expected.
Also
Hmmm... I thought I had a ticket for the connect_errors failure, but I
don't see it now. Maybe I just talked about it on IRC.
I haven't played with this for a few weeks, but as I recall Windows is
simply refusing to timeout the connection. If connect_errors.t is
modified to use the Connect
Could someone have a look at bug #50907 ?
"t/30_loops/select/connect_errors.t failure on Win32 (blocks ActiveState PPM
auto-packaging)"
http://rt.cpan.org/Public/Bug/Display.html?id=50907
