Niko Tyni wrote: > found 343690 5.0.10-10 very probably 5.0.10-10 has the bug, but does 5.10.0-10 have it? :P
> On Sun, May 11, 2008 at 09:35:01PM +0200, [EMAIL PROTECTED] wrote: > > This bug should be fixed in latest perl_5.10 with latest libc6_2.7 > > Please test it and reopen otherwise. > > I can still reproduce the crash in an SMP amd64 xen domain with > the first test script (the one by Jamil Djadala) in the report and > vm.overcommit_memory=2 on current sid: perl 5.10.0-10, glibc 2.7-11. The > kernel is from Etch, though, which actually might matter. Reopening > anyway. > > The bug doesn't usually show up on the first try; see below. It looks > like the system runs out of memory doing the perl_clone(), and something > can't quite cope. The resulting core file is obscenely big. The number > of Perl_*_dup calls and the final crashing place in the stack trace varies. > > Roberto, do you know something more about this, or what was it that > prompted you to close the bug? I just wanted to know if this bug was still applicable to latests versions. Is this bug already known by upstream perl developers? Ahora también puedes acceder a tu correo Terra desde el móvil. Infórmate pinchando aquí. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
