New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Absence of POSIX::_SC_OPEN_MAX on Windows makes perl debugger restart fail [includes workaround] #11235
Comments
From louis.strous@gmail.comThis is a bug report for perl from louis.strous@gmail.com, SUMMARY: Absence of POSIX::_SC_OPEN_MAX on Windows makes perl debugger Reported by: Louis Strous, louis.strous@gmail.com, 2011-04-04 PERL VERSION: 5.12.3, 5.10.1, 5.008008 REPRODUCTION SCENARIO: Start debugger for some perl script, enter "R" SESSION LOG: C:\Users\swtester\Documents>perl -d A.pl Loading DB routines from perl5db.pl version 1.33 Enter h or `h h' for help, or `perldoc perldebug' for more help. main::(A.pl:1): print "in A\n"; DB<1> R DB<1> R C:\Users\swtester\Documents> DIAGNOSIS: my $max_fd = 1024; # default if POSIX can't be loaded POSIX Is available but POSIX::_SC_OPEN_MAX is not defined on Windows. VERIFICATION OF DIAGNOSIS: use strict; my $max_fd = 1024; Get output: C:\Users\swtester\Documents>perl A.pl C:\Users\swtester\Documents> If no exception occurred, then at least a "Done." message should have WORKAROUND: my $max_fd = 1024; # default if POSIX can't be loaded Then on Windows the default value of 1024 gets used for $max_fd, just Flags: Site configuration information for perl 5.12.3: Configured by gecko at Wed Feb 9 14:35:46 2011. Summary of my perl5 (revision 5 version 12 subversion 3) configuration: Platform: Locally applied patches: @INC for perl 5.12.3: Environment for perl 5.12.3: |
From @cpansproutOn Mon Apr 04 01:43:59 2011, louis.strous@gmail.com wrote:
Thank you. Applied as 5332cc6. Does anyone know how to write a test for this? |
The RT System itself - Status changed from 'new' to 'open' |
I think we can call that a no :) |
Migrated from rt.perl.org#87740 (status was 'open')
Searchable as RT87740$
The text was updated successfully, but these errors were encountered: