|
From: Nicholas N. <nj...@ca...> - 2003-11-13 22:55:49
|
On Thu, 13 Nov 2003, Melchior FRANZ wrote:
> 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.
I'm sorry, I don't understand. These errors you want to attach GDB to --
are they being suppressed? It would help if you could explain what you're
doing in more detail. Thanks.
N
|