Philipp Frauenfelder <[EMAIL PROTECTED]> writes: [...]
> And as I can tell from earlier occurences of the same problem, a > recompile against the newest valgrind should suffice. However, my > first try did not succeed as valgrind has changed some paths in the > packaging or is missing some include files. I will look into this > problem later...or maybe you have time, knowledge and feel like > looking into it? I'm not sufficiently worried to spend the time, I'm afraid. I had a quick look on the mailing lists, and the suggestion there was that the CVS version of callgrind would work. Presumably it'll be fixed upstream once valgrind 2.4 is released. I wouldn't blame you if you just waited and worked on packaging that. [...] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
