Re: PM module processing problem

If you know that this internally developed module has worked in the past, I'd be less concerned about your version of Jcode (unless you just recently upgraded it).

I'd suggest you do two things:

1. Inspect what is being passed into the statement above. Since it looks like you are taking the zero index element of the default array, how big is the array?

2. Develop a quick test script that also require's the Amazon::DistributionCenter::SJISTermFilter module. If it works, there is something else causing the memory problem besides just requiring the module.

FWIW, I've never worked with Jcode before, so I'm just passing on some general ideas.

Comment on Re: PM module processing problem

Replies are listed 'Best First'.
Re^2: PM module processing problem by kmullin (Acolyte) on Dec 07, 2007 at 21:41 UTC
Thank you for your 'general ideas', that's all I'm looking for. The module is very large, so I've already got a minimal example. It is: #!/apollo/bin/env perl + # This is one of the most unbelievably hackish things I've ever done, # but it seems to be the only way to get this script to run in perl-5. +8 # while still allowing other scripts on this server to run in perl-5.6 # -davkent BEGIN { print "Removing perl.5.6.0 libraries\n"; my $cntr = 0; foreach $path(@INC) { if($path =~ /(.)(perl.5.6.0)(.)/) { print "Removing $path\n"; $INC[$cntr] = '.'; } $cntr++; } unshift @INC, "/home/kmullin/Jcode-2.06"; print "Done removing perl libraries\n"; print "Path is now:\n"; foreach $path(@INC) { print $path . "\n"; } } use Amazon::DistributionCenter::Setup; print "hello world.\n"; [download] The shebang is something we need to do around here to set up the environment, the BEGIN block is to eliminate perl 5.6 libraires, so that we can use 5.8. If you remove the entire begin block, it still gets 'Out of Memory'. It never makes it to print 'Hello, world'. By the way, I just added the unshift command in here as a way to get JCode version 2.06 into the picture. I thought that the problem may be caused by our JCode being 2.03, needing 2.06. I downloaded 2.06, put it into /home/kmullin/Jcode-2.06 thinking that perl would find it there, but its not working, it still hangs, making me think the problem is somewhere else.	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: PM module processing problem
by kmullin (Acolyte) on Dec 07, 2007 at 21:41 UTC

Thank you for your 'general ideas', that's all I'm looking for. The module is very large, so I've already got a minimal example. It is:

#!/apollo/bin/env perl
                                                                      
+                                                       
# This is one of the most unbelievably hackish things I've ever done,
# but it seems to be the only way to get this script to run in perl-5.
+8
# while still allowing other scripts on this server to run in perl-5.6
# -davkent
BEGIN {
    print "Removing perl.5.6.0 libraries\n";
    my $cntr = 0;
    foreach $path(@INC) {
       if($path =~ /(.*)(perl.5.6.0)(.*)/) {
         print "Removing $path\n";
         $INC[$cntr] = '.';
       }
        $cntr++;
     }
    unshift @INC, "/home/kmullin/Jcode-2.06";
    print "Done removing perl libraries\n";
    print "Path is now:\n";
    foreach $path(@INC) {
       print $path . "\n";
    }
}
use Amazon::DistributionCenter::Setup;
print "hello world.\n";
[download]

The shebang is something we need to do around here to set up the environment, the BEGIN block is to eliminate perl 5.6 libraires, so that we can use 5.8. If you remove the entire begin block, it still gets 'Out of Memory'. It never makes it to print 'Hello, world'. By the way, I just added the unshift command in here as a way to get JCode version 2.06 into the picture. I thought that the problem may be caused by our JCode being 2.03, needing 2.06. I downloaded 2.06, put it into /home/kmullin/Jcode-2.06 thinking that perl would find it there, but its not working, it still hangs, making me think the problem is somewhere else.

[reply]
[d/l]