On Tue, Jan 19, 2010 at 03:32:36AM +0100, Cyril Brulebois <k...@debian.org> was heard to say: > Only keeping the #include line is sufficient, I can't reproduce this > issue double free issue.
Weird. It looks like the build succeeded on all the release architectures, so I think I might downgrade this so that aptitude can get into testing. (the version currently there is ancient and I don't really want it to be held up even further by problems on one of the experimental archs now that it seems to work everywhere else) > (The waitpid() issue still has to be investigated. But I see it also > happens on other architectures, like amd64.) The waitpid() thing turned out to be mostly spurious; I've fixed it in head. I can't see how it would have caused a double-free, though. One of the tests is supposed to fork a child and check that its temporary files get deleted when it calls exit() (testing an atexit handler). I forgot to write explicit code for the child process in the switch, so it tried to wait on PID 0, then continued running tests -- that's what the failure message is from. The parent's test succeeded, although it wasn't really testing the behavior it was supposed to test. Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
