Of course it's a bug, at least a quality of implementation one. If valgrind can do it, so can gdb. Even more so, because gdb _did_ do this in the past. It certainly is a regression in gdbs stack walker, and you should try to find out what it caused.
Of course it's a bug, at least a quality of implementation one. If valgrind
can do it, so can gdb. Even more so, because gdb _did_ do this in the past.
It certainly is a regression in gdbs stack walker, and you should try to find
out what it caused.