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
on Win32 exec LIST does not quote first argument #14536
Comments
From @wchristianI tested this with AP 5.16, and SP 5.20.2, and as such assume the behavior to be present in all Perl versions, on Win7-64. I tested it by running oneliners in a cmd shell and capturing the kernel events with procmon. As follows are the oneliners run, their truncated output and their respective event attributes. Please note the lack of quotes on the exec call: -- perl -e "my @call = ('d:/s p/perl/bin/perl' ,'-v'); system(@call)" This is perl 5, version 20, subversion 2 (v5.20.2) built for MSWin32-x86-multi-thread-64int [...] -- Operation: Process Create Operation: Process Start -- perl -e "my @call = ('d:/s p/perl/bin/perl' ,'-v'); exec(@call)" Can't open perl script "p/perl/bin/perl": No such file or directory -- Operation: Process Create Operation: Process Start |
From @ikegamiOn Mon, Feb 23, 2015 at 5:00 AM, Christian Walde <perlbug-followup@perl.org>
I can't replicate. AP 5.16.3 x86, Win7-64.
This is perl 5, version 16, subversion 3 (v5.16.3) built for Copyright 1987-2012, Larry Wall Binary build 1603 [296746] provided by ActiveState Perl may be copied only under the terms of either the Artistic License or Complete documentation for Perl, including FAQ lists, should be found on |
The RT System itself - Status changed from 'new' to 'open' |
From @ikegamiah. nevermind. system works, but not exec. |
From @tonycozOn Mon Feb 23 02:00:00 2015, Mithaldu wrote:
Unlike system() and now list pipe open, Perl just calls the C run-time So we could fix exec() by re-implementing it for Win32 (not for 5.22) but there Tony |
Migrated from rt.perl.org#123907 (status was 'open')
Searchable as RT123907$
The text was updated successfully, but these errors were encountered: