Hi --
New POE user, trying to install 0.25 on cygwin/Win2K (CPAN install),
encountered several issues:
1. t/22_wheel_run......Possible memory corruption: ioctl overflowed 3rd
argument at
POE/Wheel/Run.pm line 281.
POE::Kernel's run() method was never called.
The code in question is just passing along the local window size...
# Set the pty conduit (slave side) window size to our window
# size. APITUE 19.4 and 19.5.
if (defined TIOCGWINSZ) {
if (-t STDIN) {
my $window_size = '';
ioctl( STDIN, TIOCGWINSZ, $window_size ) or die $!;
ioctl( $stdin_read, TIOCSWINSZ, $window_size ) or die $!;
}
else {
carp "STDIN is not a terminal. Can't set slave pty's window
size";
}
}
Pre-extending the window_size buffer seems to avoid the problem:
my $window_size = 'x' x 25; # 25 is probably plenty big
enough
2. t/08_errors.........FAILED test 21
Test 21 is a POE::Wheel::SocketFactory test with bogus SuccessEvent and
FailureEvent values. It seems to be failing when it attempts to listen on
the socket without first binding it. t/08_errors.t does not provide
SocketFactory with a BindPort argument for test 21, but when I add one, it
succeeds just fine. I suppose the test should find a free port somehow and
include it, but I don't know what issues this raises on other platforms.
The listen() on Solaris appears to have no issue with the same code.
It installed on my laptop with the above adjustments, and runs my app as
well as it does on Solaris. Portable development platform! w00t!
I haven't seen much concerning cygwin issues in this forum... that's either
really good or it means nobody is using POE with cygwin. ActiveState and
cygwin appear to be the only choices for Windows... can anyone summarize the
relative merits vis a vis POE applications? Anybody actually deploying real
apps using cygwin?
Any info is appreciated --
Alan
---------------------
Alan Hastings
ahastings circle-a dynamicsoft.com
