Subject: | PERL_FUTURE_DEBUG and perl 5.14.x |
This isn't really an issue in Future.pm - it's a Perl bug which Carp.pm triggers:
https://rt.cpan.org/Public/Bug/Display.html?id=72467
however due to the use of Carp message formatting, it means it's quite easy to run into messages like
panic: attempt to copy freed scalar 183d588 to 1854078
when PERL_FUTURE_DEBUG=1. Not really sure what to suggest - later versions of perl don't seem to be as susceptible to this issue, although
https://rt.perl.org/Public/Bug/Display.html?id=42166
is still open. There's a patch in the Carp.pm ticket which avoids the error (haven't checked to see if it's a good workaround), if it's somehow possible to use the same approach in Future.pm that might make debugging a bit easier on older versions of perl?
cheers,
Tom