Ok, checked again, the previous assumption was a bad guess. The problem is, it looks like heap corruption but it can have happened a while before the actually crash.
Maybe the tester could export MALLOC_CHECK_=2 in the startup environment so the heap corruption detection is executed. But honestly, I would only test the last version because 0.5.6 has been released a year ago and in the meantime, there were bugfixes all around this place. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/649009 Title: apt-cacher-ng crashed with SIGSEGV in malloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/649009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
