I tried to bring some light through code review, and there is nothing suspicious at the first (and at the second) glance. The best theories I have are: a) bug in one of the regex functions (libc issue), b) stack corruption (might be detectable with lintian, not sure), c) some race in thread destruction. But all are a way off the track.
What do you recommend to reproduce it, using a lucid/i386 chroot for a while? -- apt-cacher-ng assert failure: *** glibc detected *** /usr/sbin/apt-cacher-ng: malloc(): corrupted unsorted chunks 2: 0x09e7a4e0 *** https://bugs.launchpad.net/bugs/532353 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
