I got a similar problem just this morning. I have a perl script that has problems getting parsed correctly (on i386 Suse-Linux in an utf8 environment). In one case 'perl -c script.pl' even results in a segmentation fault.
The effect vanishes as soon as I add 'use utf8;' to the script which hints at the cause of the problem.
Will update to perl 5.8.8 and see what that does.
Update:
My problem still exists with perl 5.8.8:
> perl -c EB/vb.pm
*** glibc detected *** malloc(): memory corruption (fast): 0x000000000
+071f880 ***
Abbruch
If someone wants to try out, this produces a segmentation fault on my machine:
package EB::Parse;
use strict;
use 5.008;
use warnings;
use encoding 'utf8';
use Carp;
my($parser);
$parser= q{
{ my $execute=0; }
all : /[:\\s]*/ zeitortobjekt(s? /[:\\s]*/) befehl(s? /[:\\ ]*/) /.*
+/
gug : '1'
#------------
};
1;
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.