in reply to Re^2: Filehandle open fails in script packed with PAR::Packer
in thread Filehandle open fails in script packed with PAR::Packer

Ok, next step get depends.exe /c /f:1 /pb /ot:temp.txt ... openfile_test.exe ... and see what you can figure out

Or next step upgrade to a supported version of perl (5.14 is expired) and upgrade as much of everything (PAR/Tk...) as you can :)

  • Comment on Re^3: Filehandle open fails in script packed with PAR::Packer

Replies are listed 'Best First'.
Re^4: Filehandle open fails in script packed with PAR::Packer
by elef (Friar) on Jan 14, 2014 at 22:05 UTC
    It spat out 3000 lines of stuff. I can't make much sense of it except for the last line: "Exited "OPENFILE_TEST.EXE" (process 0x18AC) with code -1073741819 (0xC0000005)." This is the same error code I posted above (access violation).
    I should note that if I move the open out of the sub, it works. Like so:
    # BITS OF CODE CHOPPED OFF my $buttbrowse = $bin_win -> Button(-text=>"Browse", -command => sub { +filepicker}) -> pack(-pady => 20); open (OUT, ">:encoding(UTF-8)", "c:/test/filepath.txt") or print "Can' +t open file: $!"; # this fails when the script is packed into an e +xe with PAR::Packer print OUT "File path: how would I know if I get printed before the sub + runs?"; close OUT; MainLoop;
    Of course this doesn't fix the problem because the variable I want to print to the file is filled in by the sub. But it does indicate something about the error perhaps. I would like to know if this error occurs for other people. I'd think not.

      It spat out 3000 lines of stuff. I can't make much sense of it except for the last line

      I already saw that one, it doesn't mean anything, it means "access denied to memory", so try looking at the line above

      or watch it in visual mode of depends ... like shown in one of the links, the errorings shows up in read, so look at last one, look above ...

      I should note that if I move the open out of the sub, it works.

      That would make me assume the encoding modules/files weren't packed completely or the wrong one is picked up or something else entirely ...

      The next steps are exactly the same as I outlined in my previous linksss