Bug #45403 for PAR: Program too big to fit in memory

Fri Apr 24 15:28:19 2009 Richard.Lai [...] freescale.com - Ticket created

CC:	"Lai Richard-RA3981" <Richard.Lai [...] freescale.com>
Subject:	Program too big to fit in memory
Date:	Fri, 24 Apr 2009 12:27:27 -0700
To:	<bug-PAR [...] rt.cpan.org>
From:	"Lai Richard-RA3981" <Richard.Lai [...] freescale.com>

Download image001.gif
image/gif 5k

I'm running PAR & pp on Windows XP to generate a standalone .exe. Resulting .exe runs on a different computer just fine, but gives a "Program too big to fit in memory" error on another. Both computers are running XP as well with at least 1GB RAM. Am running ActivePerl 5.10.0 Build 1004. The test script is short: #! /usr/bin/perl -w #use strict; print "\nHello World\n\n"; sleep(5); I've tried pp -m option without any success. I also tried the evaluation version of perl2exe with no success. I have verified the paging file on both computers and they are bigger than the 384MB I have. I have also tried running the .exe in compatibility mode with no success. There doesn't appear to be any differences for autoexec.nt and config.nt. Thanks, Richard NMG Product Engineering Freescale Semiconductor, Inc. Phone: 512.895.7365 Fax: 512.895.3051 E-mail: Richard.Lai@Freescale.com <mailto:Richard.Lai@Freescale.com> This e-mail, and any associated attachments have been classified as: Freescale Semiconductor General Business Freescale Semiconductor Internal Use Only Freescale Semiconductor Confidential Proprietary

Wed Aug 26 10:01:41 2009 smueller [...] cpan.org - Correspondence added

Hi Richard, apologies for the delay in replying. On Fri Apr 24 15:28:19 2009, Richard.Lai@freescale.com wrote: Show quoted text

> I'm running PAR & pp on Windows XP to generate a standalone .exe. > Resulting .exe runs on a different computer just fine, but gives a > "Program too big to fit in memory" error on another. Both computers are > running XP as well with at least 1GB RAM. Am running ActivePerl 5.10.0 > Build 1004.

Is this a 32 vs. 64bit issue? Show quoted text

> The test script is short:

[snip test script] This is very, veeeery likely not at all related to your test script. Show quoted text

> I've tried pp -m option without any success. I also tried the > evaluation version of perl2exe with no success. > > I have verified the paging file on both computers and they are bigger > than the 384MB I have. I have also tried running the .exe in > compatibility mode with no success. There doesn't appear to be any > differences for autoexec.nt and config.nt.

From my very distant and limited experience with Windows, you get similar errors if you try to run an executable that was not generated for the platform at hand. Actually, I wouldn't even be surprised if you could simply rename an arbitrary file to an .exe and run it to get the same error. I'll wager that this is not even a PAR bug at all but simply non-binary-compatible systems (and thus marking the bug as rejected, but feel free to reply with more input: It will be automatically reopened! The history of the ticket is NOT erased either!) This is supported by the fact that the entirely unrelated perl2exe tool produces the same problems. As an extra test, you can copy the parl.exe PAR loader from the source to the target machine and try running it. If it doesn't run, you at least know that your perl code is not at all involved in the issue, but that it's a problem with the binary/C/loader part of the tool chain. Cheers, Steffen

Wed Aug 26 10:01:43 2009 The RT System itself - Status changed from 'new' to 'open'

Wed Aug 26 10:01:49 2009 smueller [...] cpan.org - Status changed from 'open' to 'rejected'