Lines Matching full:reported
124 stands for "not in bugzilla" -- that is, a bug that was reported to us
311 stands for "not in bugzilla" -- that is, a bug that was reported to us
560 stands for "not in bugzilla" -- that is, a bug that was reported to us
949 pthread_barrier_destroy() calls are now reported.
1087 stands for "not in bugzilla" -- that is, a bug that was reported to us
1160 186790 Suppression pattern used for leaks are not reported
1258 bugzilla" -- that is, a bug that was reported to us but never got a
1403 "not in bugzilla" -- that is, a bug that was reported to us but
1478 bugzilla" -- that is, a bug that was reported to us but never got a
1673 "not in bugzilla" -- that is, a bug that was reported to us but
1788 bugzilla" -- that is, a bug that was reported to us but never got a
1870 bugzilla" -- that is, a bug that was reported to us but never got a
1964 - The number of undefined-value errors incorrectly reported by
2020 the exit code in runs where Valgrind reported errors, which is
2122 3.1.1 fixes a bunch of bugs reported in 3.1.0. There is no new
2348 3.0.1 fixes a bunch of bugs reported in 3.0.0. There is no new
2717 99923 0-sized allocations are reported as leaks
2784 This bug was reported multiple times, and so the following
3345 them, and tend to fix the most frequently reported bugs.
3413 Several people reported this. If you had floating point code which
3434 is now memcheck.h. Some people reported problems and strange
