Skip Menu |

This queue is for tickets about the PAR CPAN distribution.

Report information
The Basics
Id: 7299
Status: resolved
Priority: 0/
Queue: PAR

People
Owner: Nobody in particular
Requestors:
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.85
Fixed in: (no value)



Subject: -C option hangs script on Win32 with PAR .85
Operating System: Windows XP Perl version: v5.8.3 PAR version: .85 Scripts created with the -C option seems to hang indefinitly and take all remaining CPU cycles. If you remove the -C the PAR generated scripts run fine. I don't remember this being an issue prior to .85.
[guest - Mon Aug 9 10:37:56 2004]: Show quoted text
> Operating System: Windows XP > Perl version: v5.8.3 > PAR version: .85 > > Scripts created with the -C option seems to hang indefinitly and take > all remaining CPU cycles. If you remove the -C the PAR generated > scripts run fine. I don't remember this being an issue prior to .85. >
Having the exact same problem on winXP SP2, activestate perl 5-8-6 multi-thread - pp 0.12 / PAR 0.87 - DBI 1.48 : if I simply do : pp -C -e "use DBI; print qq(quitting\n)' it generates a script that never quits after printing. Same script without '-C' behaves as expected. If I remove the 'use DBI', both -C and non -C version work ok.
On Mi. 04. Mai 2005, 13:33:38, guest wrote: Show quoted text
> [guest - Mon Aug 9 10:37:56 2004]: >
> > Operating System: Windows XP > > Perl version: v5.8.3 > > PAR version: .85 > > > > Scripts created with the -C option seems to hang indefinitly and take > > all remaining CPU cycles. If you remove the -C the PAR generated > > scripts run fine. I don't remember this being an issue prior to .85. > >
> > Having the exact same problem on winXP SP2, activestate perl 5-8-6 > multi-thread - pp 0.12 / PAR 0.87 - DBI 1.48 : > > if I simply do : > pp -C -e "use DBI; print qq(quitting\n)' > > it generates a script that never quits after printing. Same script > without '-C' behaves as expected. If I remove the 'use DBI', both -C and > non -C version work ok. > >
Hi and sorry for the late answer. I have witnessed this behaviour only for incompatible PAR/perl+XS-modules versions. I could not reproduce the problem on my win32 system which naturally has compatible versions because I built PAR myself. Could you retry with the most current version of PAR (0.959) and see whether this issue still comes up? If so, just reply to this mail and - as time permits - I'll try to look into it. Thanks, Steffen