Bug #4618 for PAR: Can't spawn "C:\Perl\bin\parl.exe": No error at c:\Perl\bin\pp line 341

Tue Dec 09 14:20:16 2003 Guest - Ticket created

Subject:

Can't spawn "C:\Perl\bin\parl.exe": No error at c:\Perl\bin\pp line 341

This is the same problem I reported a while ago on IRC, just putting it here so it's not forgotten and attaching foo.exe which also demonstrates the problem: C:\Perforce\VCP>echo print(qq{hi\n}) > foo.pl && pp -o foo.exe foo.pl Can't spawn "C:\Perl\bin\parl.exe": No error at C:\Perl\bin\pp line 341. C:\Perforce\VCP>echo print(qq{hi\n}) > foo.pl && pp -o foo.exe foo.pl Can't spawn "C:\Perl\bin\parl.exe": No error at C:\Perl\bin\pp line 341. C:\Perforce\VCP>echo print(qq{hi\n}) > foo.pl && pp -o foo.exe foo.pl Can't spawn "C:\Perl\bin\parl.exe": No error at C:\Perl\bin\pp line 341. C:\Perforce\VCP>echo print(qq{hi\n}) > foo.pl && pp -o foo.exe foo.pl C:\Perforce\VCP>perl foo.pl hi C:\Perforce\VCP>foo.exe hi C:\Perforce\VCP>foo.exe C:\Perforce\VCP>foo.exe C:\Perforce\VCP>foo.exe hi C:\Perforce\VCP>

Download foo.exe
application/octet-stream 1.2m

Message body not shown because it is not plain text.

Tue Dec 09 14:38:35 2003 Guest - Correspondence added

From:

barries [...] slaysys.com

More details: This is on WinXPPro, SP1 to us non-MS-versioning droids, and it's running inside VMware. Perl and other non-parl based executables run thousands of times a day. The parl-based executables seem to have trouble. Using a WinXX strace utility, it looks like perl's reading extra data in from the archive file somehow, not sure. C:\Perforce\VCP>uname -a Windows NT slaysys 5.1 Build 2600 (Service Pack 1) x86 C:\Perforce\VCP>perl -V Summary of my perl5 (revision 5 version 8 subversion 0) configuration: Platform: osname=MSWin32, osvers=4.0, archname=MSWin32-x86-multi-thread uname='' config_args='undef' hint=recommended, useposix=true, d_sigaction=undef usethreads=undef use5005threads=undef useithreads=define usemultiplicity=define useperlio=define d_sfio=undef uselargefiles=define usesocks=undef use64bitint=undef use64bitall=undef uselongdouble=undef usemymalloc=n, bincompat5005=undef Compiler: cc='cl', ccflags ='-nologo -Gf -W3 -MD -Zi -DNDEBUG -O1 -DWIN32 - D_CONSOLE -DNO_STRICT -DHAVE_DES_FCRYPT -DPERL_IMPLICIT_CONTEX T -DPERL_IMPLICIT_SYS -DUSE_PERLIO -DPERL_MSVCRT_READFIX', optimize='-MD -Zi -DNDEBUG -O1', cppflags='-DWIN32' ccversion='', gccversion='', gccosandvers='' intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234 d_longlong=undef, longlongsize=8, d_longdbl=define, longdblsize=10 ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='__int64', lseeksize=8 alignbytes=8, prototype=define Linker and Libraries: ld='link', ldflags ='-nologo -nodefaultlib -debug -opt:ref,icf - libpath:"C:\Perl\lib\CORE" -machine:x86' libpth="C:\Perl\lib\CORE" libs= oldnames.lib kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib netapi32.lib uuid.lib wsock32.lib mpr.lib winmm.lib version.lib odbc32.lib odbccp32.lib msvcrt.lib perllibs= oldnames.lib kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32 .lib netapi32.lib uuid.lib wsock32.lib mpr.lib winmm.lib version.lib odbc32.lib odbccp32.lib msvcrt.lib libc=msvcrt.lib, so=dll, useshrplib=yes, libperl=perl58.lib gnulibc_version='undef' Dynamic Linking: dlsrc=dl_win32.xs, dlext=dll, d_dlsymun=undef, ccdlflags=' ' cccdlflags=' ', lddlflags='-dll -nologo -nodefaultlib -debug - opt:ref,icf -libpath:"C:\Perl\lib\CORE" -machine:x86' Characteristics of this binary (from libperl): Compile-time options: MULTIPLICITY USE_ITHREADS USE_LARGE_FILES PERL_IMPLICIT_CONTEXT PERL_IMPLICIT_SYS Locally applied patches: ActivePerl Build 806 Built under MSWin32 Compiled at Mar 31 2003 00:45:44 %ENV: PERL5LIB="C:\Perforce\VCP\lib" @INC: C:\Perforce\VCP\lib C:/Perl/lib C:/Perl/site/lib .

Wed Dec 10 21:26:41 2003 Guest - Correspondence added

Subject:

Also occurs with ActiveState's 5.8.1

The same problem occurs after upgrading from 5.8.0 to 5.8.1. - Barrie

Thu Dec 11 16:20:27 2003 Guest - Correspondence added

Subject:	Might be a VMware vs. parl.exe issue
From:	barries [...] slaysys.com

[guest - Tue Dec 9 14:20:16 2003]: I have no idea why, but running the foo.exe on a real physical machine seems to work. What could parl.exe be doing that would trip up in a virtual machine and not in a physical machine? - Barrie

Fri Apr 30 12:09:36 2004 autrijus [...] cpan.org - Correspondence added

[guest - Thu Dec 11 16:20:27 2003]: Show quoted text

> [guest - Tue Dec 9 14:20:16 2003]: > I have no idea why, but running the foo.exe on a real physical machine > seems to work. > > What could parl.exe be doing that would trip up in a virtual machine > and not in a physical machine?

Hey Barries. Is this bug still relevant to you? Thanks, /Autrijus/

Fri Apr 30 12:09:37 2004 autrijus [...] cpan.org - Status changed from 'new' to 'stalled'

Fri Apr 30 13:40:55 2004 autrijus [...] cpan.org - CustomField Important deleted

Sun Jul 16 08:46:09 2006 smueller [...] cpan.org - Status changed from 'stalled' to 'resolved'