On Mon, Nov 08, 2010 at 11:51:07AM +0100, Paul Slootman wrote: > On Mon 08 Nov 2010, Niko Tyni wrote: > > > > did you ever find out what caused this? Are you still seeing those messages? > > At the time I downgraded to the 5.10.0-19 version that wasn't affected > by this problem. 5.10.0-25 _is_ affected. > > I'm not able to upgrade to the current testing, as that requires a new > libc that requires a newer kernel and I haven't been able to get a newer > kernel working on my alpha system :( > > It may have been fixed in 5.10.1, but I don't think I can try that... > I don't mind if you mark this bug unreproducible and close it after > squeeze has been released.
It's not unreproducible. Now that I tried, I see the same messages with the perl 5.10.1-16 test suite on albeniz.d.o when building with gcc-4.3 (4.3.5-4) but not with gcc-4.4 (4.4.5-6). The default gcc version changed to gcc-4.3 right after the Lenny release, and the first perl version built with it was 5.10.0-21. The switch to gcc-4.4 happened in December 2009, and the first perl version built with that was 5.10.1-9. Therefore I expect your problem is fixed with 5.10.1-9. It's not clear at all if this is a Perl bug or a GCC one. I'm not particularly interested in digging deeper unless it manifests itself again with newer gcc versions. Are you OK with closing this bug at 5.10.1-9? -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
