develooper Front page | perl.par | Postings from September 2018

RE: [ #127064] Question about weird pp executablebehavior

Thread Previous | Thread Next
Chenchen Qu via RT
September 10, 2018 19:43
RE: [ #127064] Question about weird pp executablebehavior
Message ID:
Mon Sep 10 15:43:16 2018: Request 127064 was acted upon.
Transaction: Correspondence added by
       Queue: PAR-Packer
     Subject: RE: [ #127064] Question about weird pp executable behavior
   Broken in: (no value)
    Severity: (no value)
       Owner: RSCHUPP
      Status: open
 Ticket <URL: >

Hi Roderich:

1. yes we save the @ARGV in our logs so we know exactly what the input is.
2. Weird thing is, I checked the client environment variable, there 's nothing special, both TEMP and TMP are defined as the local temp directory, nothing related with PAR_*. The only thing that raised my attention is the client also have perl installed on the instance, do you think that might cause the DynaLoader to load the wrong libraries and trigger an issue like this?

I'm going to suggest the client to run our application on a clean vm, so this probably won't happen. Will update with the result. 


-----Original Message-----
From: Roderich Schupp via RT <> 
Sent: Monday, September 10, 2018 2:04 AM
To: Chenchen Qu <>
Subject: [ #127064] Question about weird pp executable behavior

<URL: >

Hi Chenchen,

On 2018-09-07 10:58:42, wrote:
> When they run the executable file, the cache directory was input as 
> the first argument, for example When they do run.exe --setup the 
> actual input was run.exe
> Sonntag\AppData\Local\Temp\par-4a616e20536f6e6e746167\cache-
> 1535125512/run.exe --setup

Just curious: how did you find out? Did you something like

pp -o run.exe -E "say qq[@ARGV]"

and had the client run this run.exe?

> I think this might be some bad setup with their PATH variable, but I'm 
> not 100% sure since I can't reproduce this on any VMs.
> Any suggestion is appreciated.

I can't think of something that would produce this effect...
I would check the following environment variables in the client's environment whether they contain "unusual" characters (e.g. blanks): TMPDIR, TEMPDIR, TMP, TEMP and PATH. Also, are there any environment variables that start with PAR_?

Note that the way how command line arguments are passed to the packed executable changed in PAR::Packer 1.038 and later.
Could you prepare a test executable like the above packed with the latest PAR::Packer and have the client run it?

Cheers, Roderich

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About