ActivePerl discussion

Perl and ActivePerl usage questions; Perl practices and programming questions; Perl questions that don't fit other categories

Perl CVE-2013-1667 Input Rehashing Denial of Service Vulnerability

Does this apply to active perl I know that it applies to the more generic version of Perl 5.14.x. Will ActiveState release a product specific patch to address this issue?

Using Perl 5.16, Win32::DirSize does not work.

What do I use to get the number of files and directories in an upper directory. Win32::DirSize no longer works with 5.16 Perl.

can no longer store a database handle in an environment variable

After installing ActivePerl 5.24.0, we can no longer store a database handle in an environment variable.

We get the following error when trying to prepare a sql statement:

Can't locate object method "prepare" via package

The scripts works when I change the database handle from an environment variable to a local variable.

Is there an easy fix for this or do I have to change all of our code to use local variables to store a database handle?

Permission denied


I've installed ActivePerl 32 bits version.
perl -v
gives the right answer.

When I want to run a script, I get a "permission denied" message each time I want to open a file.

I tried the following code :

open (OUT1,">out1.txt") or die "Cannot: $!";
print OUT1 "testing\n";
close (OUT1);

and then ran it in cmd window (Administrator or not, it does not change anything) :
Cannot: Permission denied at line 1.

Issues setting up GCC and GDB with Activestate


I am having issues configuring GCC/GDB with Activestate perl (v5.22.3 built for MSWin32-x64-multi-thread). Installing the toolchain works well (ppm install mingw) and I can build the module (perl, XS, C) in question, but it crashes at runtime. The same module compiles and runs under strawberry perl and doesn't crash. I am trying to track down the cause of the crash, but I can't get GDB to produce any decent output:

(gdb) bt
#0  0x000000006865b3a8 in ?? ()
#1  0x0000000000725db9 in ?? ()
#2  0x0000000000725d08 in ?? ()
#3  0xffffffffffffffff in ?? ()

Various failure when attempting to update libraries, e.g. Text::CSV

Greetings - I'm trying to do updates to various libraries in ActivePerl, and failing spectacularly. I'm wondering if I can get some assistance - would be greatly appreciated.

Starting from the top - I'm trying to use Text::CSV, and getting a failure "Can't locate auto/Text/CSV/ in @INC...". A google search shows that I'm using a really old version of Text::CSV - version 0.5. I see that version 1.91 is the latest.

Perldoc fail: invalid argument -R

I recently installed v5.24.1 form MSWin32-x64, replacing an earlier version. Perldoc now fails every time with a message "Invalid parameter - -R"

I have searched the Net for this error and found a few people asking the question but no answers. Evidently it is a Windows-only problem not occurring in Unix.

Erronous error message related to nmake.exe not in PATH

Steps to reproduce the problem:
Using ActivePerl and OpenSSL 1.1.0c run "perl Configure VC-WIN64A" from a Visual Studio 2015 command prompt.

Actual result:
The following error will be presented:
It looks like you don't have either nmake.exe or dmake.exe on your PATH,
so you will not be able to execute the commands from a Makefile. You can
install dmake.exe with the Perl Package Manager by running:

ppm install dmake

Expected result:
No error will be presented.

Windows scripting host broken again in 5.22 and 5.24 updates

Once again, Windows scripting host integration is broken in the latest 5.22 and 5.24 releases. This occurred previously in version, and was fixed in See

Can anyone look into this?

Dos dir command from within Perl produces different results in Windows 7 and Windows 10

I have an application that uses the line:

@files_ls = `dir`;

I use the result to produce a sorted list by time and I optionally only print files that match a regular expression.

The output is different between windows 7 and windows 10. The former has all the date info, the latter only produces the file name.

In a regular DOS prompt I get the same result on both systems.

Does anyone have a clue as to how to circumvent this problem?