Mike Gabriel <mike.gabr...@das-netzwerkteam.de> writes: > Sooo... My assumption was, that this was related to some package > upgrades in the archive. Maybe packages that have not reached the > archtitectures, that showed the test failures on buildd.
Thanks for the quick reply! I do wonder whether there's more to it than that, though, particularly in light of the similar if not identical errors libqtdbusmock proceeded to hit on mips (which I reported as #879942 just after you sent your reply). More specifically, this looks like the sort of error that could arise after prematurely freeing memory. Have you tried running under Valgrind, or locally building with -fsanitize=address? -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
