|
From: Dennis W. <dw...@ma...> - 2009-06-05 08:40:16
|
Julian Seward schrieb: >> --941206317-Æ Memcheck, a memory error detector > > That looks extremely strange, and it looks to me like there is some > problem in Valgrind's internal implementation of printf, or maybe in > the varargs code that gcc generates for calls to it. Are you using > some kind of hacked toolchain to build Valgrind? Did you make any > changes at all to the Valgrind sources? > > J Sorry, I completely forgot to reply-to-all. Here you go: Nope, just plain ol' gcc-4.3.3 (self-compiled, non-root install, works like a treat otherwise). The only change I had to make to valgrind is in one of the testcases, where I had to #include another header because PTHREAD_MAX_something was undefined, but valgrind itsself compiled without errors (some inliner warnings, that's all) Thanks, Dennis -- Zentrum für Technomathematik, AG Optimierung und Optimale Steuerung fon: 0421-218.63866 fax: 0421-218.9863866 web: www.worhp.de |