Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Storable CPAN distribution.

Report information
The Basics
Id: 127408
Status: open
Priority: 0/
Queue: Storable

Owner: Nobody in particular
Requestors: MLEHMANN [...]

Bug Information
Severity: (no value)
Broken in: 3.11
Fixed in: (no value)

Subject: probe for stacksizes uses installed version of Storable
Download (untitled) / with headers
text/plain 1.3k
When trying to statically build Storable, I get this output: probe for max. stack sizes... Storable object version 2.53 does not match $Storable::VERSION 3.11 at line 100. Compilation failed in require. BEGIN failed--compilation aborted. The reason is likely that the module runs stacksize, which uses Storable, before it is properly installed, so it gets the wrong version of Storable (in this case, the one that came with perl). Looking at stacksize, I am not sure what the point of it is - it seems to measure the stack size at build time, built I can't imagine what the use for this would be, as it cannot prevent stack overflow or be of use for security issues. But maybe I overlook something. However, at least on unix systems, the stack size in effect can be queried via rlimits, and this gives the correct stack size quickly and without these issues. If, for whatever reason, the stack size at build time is required, it could easily be gotten via rlimits. If this is not possible, and since a fix for this clunky behaviour might be difficult, would it be possible to allow setting a fixed stack size (e.g. via an environment variable)? This would also allow people to configure the actual stack size in use for the module, if it plays any role at runtime later (where the compile tiem stacksize would be wrong), and would allow a reasonably easy workaround for the build problems.

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to