|The stupid question is the question not asked|
Maybe Bug in Perl 5.20.0 (x86_64)? Please advice ...by linuxer (Curate)
|on Jun 05, 2014 at 22:20 UTC||Need Help??|
linuxer has asked for the wisdom of the Perl Monks concerning the following question:
At http://www.perl-community.de/bat/poard/start (a German Perl Forum) another user posted a question about a possible perl bug he discovered; the thread is http://www.perl-community.de/bat/poard/thread/19133 (not much content though...)
Unfortunately I have very little insight into Perl's internals I seek your advice, if it really is a perl bug or maybe just a "pilot error" (as erix called it ;-) )
I could follow his instructions and recreate the "bug". We both use a self compiled perl 5.20.0 (I used perlbrew for that; don't know what the other user used). The crash happens when using perl 5.20.0, but does not happen, when using 5.18.x (I used 5.18.1, the other user 5.18.2). My tested Perl versions are x86_64.
Instruction to run into the error:
What do you think? Is this a bug in Perl (maybe only in x86_64)? Or a "pilot error", but then I wonder what's that different in 5.18.1 that it does not throw such error?
Thanks in advance.
Update: I just installed 5.21.0 with perlbrew, switched to that version and installed DBD::SQLite and App::DBBrowser with cpan, and the test fails again. Currently I am thinking of how to install an 32bit perl 5.20.0 with perlbrew without interfering with the already installed 64bit perl for testing...