At Fri, 21 Jan 2005 04:06:10 +0900, Tatsuki Sugiura wrote: > > Hello, Thanks for reporting. > > >>> In Message "Bug#291360: libunicode-japanese-perl: Unicode::Japanese does > >>> not use as XS module." > >>> <[EMAIL PROTECTED]>, > >>> Chihiro Kuroki <[EMAIL PROTECTED]> said; > > I got 'Segmentation fault' using "use Unicode::Japanese;". > > > strace sample.pl > > Can you send me this sample?
Since personal information is included, please give me time to modify. > > It goes well in these after-mentioned cases. > > > 1) using "use Unicode::Japanese qw(PurePerl);". > > 2) in a chrooted IA32 environment > > 3) one character is set to an instance of Unicode::Japanese > > <Snip...> > > -- System Information: > > Debian Release: 3.1 > > Architecture: amd64 (x86_64) > > Kernel: Linux 2.6.9-10-amd64-k8 > > Sorry, I'm confused. > You got SEGV on IA32. > Then, you sent report on IA64? > Is this correct? No, it isn't. Sorry for my insufficient information. I got SEGV on X86_64 environment. But on a chrooted IA32 environment of X86_64, SEGV didn't occur. > Anyway, It seems a bug of perl. I think any pure perl module > can not cause segv without interpreter bug. From somewhere, it has been heard that malloc of 64-bit environment causes trouble. Is this SEGV related to it? -- [EMAIL PROTECTED] GnuPG fingerprint = 90FD FE79 905F 26F9 29C4 096F 8AA2 2C42 5130 1469 Chihiro Kuroki
