Mon Sep 10 02:04:01 2018: Request 127064 was acted upon.
Transaction: Correspondence added by RSCHUPP
Queue: PAR-Packer
Subject: Question about weird pp executable behavior
Broken in: (no value)
Severity: (no value)
Owner: RSCHUPP
Requestors: [email protected]
Status: new
Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=127064 >
Hi Chenchen,
On 2018-09-07 10:58:42, [email protected] 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
