https://bugs.kde.org/show_bug.cgi?id=376595
--- Comment #22 from Aetf <7437...@gmail.com> --- Okay I can reproduce your issue now. I guess the difference is that yours is multi-threaded (several threads for qt internal stuff). And when gdb stopped, it stopped at another thread different from the main thread. Probably gdb can't handle this case well. However I'm afraid there's no much I can do on the kdevelop side. As it's hard to distinguish a member variable from normal ones, and it's unclear whether this is the only condition that would trigger the bug. Maybe you should report this to gdb. In the mean time, as a workaround, you can set watchpoints in the Breakpoints tool view manually, using "this.<varname>" as the location. This works as intended. -- You are receiving this mail because: You are watching all bug changes.
