|
From: John R.
|
Julian Seward wrote: > We do have exacting users, they do communicate extensively with us > when stuff doesn't work, and we do our best to accommodate. What you > say doesn't square with the feedback we get. If we hadn't listened to > the needs of our users, Valgrind would have been a great deal less > successful than it has been. Aim higher. I have tried valgrind several times over the last 4 years, and the result of each trial has been, "memcheck cannot handle my code." The outstanding example is memcheck cannot run the internal testcases of glibc. Complete coverage of i686 user-mode opcodes also matters to me. Both of these areas have readily-available specifications. The manual and/or release notes for valgrind should list the failing cases. -- |