I thought I'd pass this along....
ActiveState has discovered a severe bug in the PerlCtrl component
of the Perl Dev Kit that may result in deletion of the filesystem. The
bug only occurs for PerlCtrls built using the -clean option.
When these controls are loaded and unloaded into memory without
actually instantiating an instance of the control, arbitrary parts of
the filesystem may be permanently deleted.
More information can be viewed here:
Note that this is not triggered when the component is used via COM or
OLE Automation. It occurs when the control is loaded from C/C++ code
using LoadLibrary/FreeLibrary. We are aware of two occasions where this
1) Registering the control with MTS
2) Adding the control to an MSI using PerlMSI
This bug is present in *all* versions of PerlCtrl released to date,
including PDK 3.1. It will be fixed in the upcoming release of PDK 4.0.
A PDK 3.1.1 release containing the fix will also be available as a free
upgrade for users of PDK 3.x.
We strongly recommend that you do not use the -clean option with PerlCtrl,
and that you rebuild controls already built using that option.
We apologize for any inconvenience this may cause.
Please direct any feedback to PDK-feedback@ActiveState.com.
Programming for the People