|
From: Melchior F. <mf...@kd...> - 2003-11-13 21:38:15
|
There's an annoying bug in valgrind 2.0.0 (and probably older
versions). I'm memchecking a program with --gdb-attach=yes and
--suppressions=file, and with (among other rules) this in my
suppressions file:
{
<foo>
Memcheck:Cond
fun:_ZNSt13basic_filebufIcSt11char_traitsIcEE18_M_really_overflowEi
fun:_ZNSt13basic_filebufIcSt11char_traitsIcEE8overflowEi
fun:_ZNSt15basic_streambufIcSt11char_traitsIcEE5sputcEc
fun:_ZN6logbuf8overflowEi
}
But valgrind doesn't stop after displaying bugs, instead everything
rushes by without prompting me to start gdb. If, however, I change
any of the "fun:" lines so that the mangled symbol doesn't match
any more, then valgrind will stop after the next bug.
m. ??
|