At Fri, 15 Apr 2005 09:39:17 +0200,
Gabor Gombas wrote:
> On Fri, Apr 15, 2005 at 09:37:09AM +0900, GOTO Masanori wrote:
>
> > Before we reassign to perl, we need to clear which setting triggers
> > your problem. At least under my environment, this problem is not
> > appeared. Could you confirm your environment settings (ex: LANG or
> > malloc related value), and perl versions?
>
> LANG=en_US.UTF-8
> LANGUAGE=en_US:en_GB:en
> LC_CTYPE=hu_HU.UTF-8
>
> ii perl 5.8.4-8 Larry Wall's Practical Extraction and Report
Hmm, I didn't reappear this problem even I set with your environment
variables. Could you dig this problem a bit more? If it's
unreproducible, perl maintainer also cannot find what the actual bug
is...
> Last few lines from "strace dpkg-reconfigure dash":
...
> 28191 close(7) = 0
> 28191 open("/dev/tty", O_RDWR|O_NONBLOCK|O_NOCTTY) = 3
> 28191 writev(3, [{"*** glibc detected *** ", 23}, {"double free or corruption
> (!prev"..., 33}, {": 0x", 4}, {"08785b58", 8}, {" ***\n", 5}], 5) = 73
> 28191 rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
> 28191 tgkill(28191, 28191, SIGABRT) = 0
> 28191 --- SIGABRT (Aborted) @ 0 (0) ---
> 28191 +++ killed by SIGABRT +++
>
>
> Compared to the last lines from "MALLOC_CHECK_=0 strace dpkg-reconfigure
> dash":
...
> 28157 exit_group(0) = ?
>
> So perl seems to be dying in exit().
Could you investigate perl with glibc 2.3.2.ds1-20 + MALLOC_CHECK_=0
to 3? If perl has double free bug, such bug should be also appeared
on sarge/sid environment.
Regards,
-- gotom
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
