Three more, only this time more relevant
C:\Documents and Settings\malcolm\My Documents\proj_pp_testing>aa.exe
Crashhhh

C:\Documents and Settings\malcolm\My Documents\proj_pp_testing>aa.exe
Crashhhh

C:\Documents and Settings\malcolm\My Documents\proj_pp_testing>aa.exe
Crashhhh
----- Original Message ----- 
From: "the.noonings" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, May 08, 2004 10:27 PM
Subject: Re: PP generates some duff code with multithreading enabled


> Works fine for me on windows XP Pro, using perl  v5.8.3 built for
> MSWin32-x86-multi-thread
>
> C:\Documents and Settings\malcolm\My Documents\proj_pp_testing>type aa.pl
> #!/usr/bin/perl
> use threads;
> use threads::shared;
>
> C:\Documents and Settings\malcolm\My Documents\proj_pp_testing>pp -o
aa.exe
> aa.pl
>
> C:\Documents and Settings\malcolm\My Documents\proj_pp_testing>aa.pl
> Crashhhh
>
> C:\Documents and Settings\malcolm\My Documents\proj_pp_testing>aa.pl
> Crashhhh
>
> C:\Documents and Settings\malcolm\My Documents\proj_pp_testing>aa.pl
> Crashhhh
>
>
> ----- Original Message ----- 
> From: "Ed Wildgoose" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, May 08, 2004 1:21 PM
> Subject: PP generates some duff code with multithreading enabled
>
>
> > Please try the following snippet through pp.  It executes fine, but
> > crashes when the app exits (at least on win32, havent tried linux yet).
> > I would be really grateful if someone could help debug this - it's the
> > last major bug standing in the way of packaging my little email app with
> > par.
> >
> > #!/usr/bin/perl
> > use threads;
> > use threads::shared;
> >
> > print "Crashhhh\n";
> > ## fails to exit cleanly after this...
> >
> >
> > Thanks for any help.
> >
> > Ed W
> >
> > P.S. Autrijus, I will try to check it out myself, but in the latest
> > pre-release did you check in Alan Stewarts changes to fix the --icon
> > problem where it increases the file size?  I have just been retesting
> > his version and it does seem to work fine for me?
> >
> > Thanks
> >
>

Reply via email to