https://bugs.kde.org/show_bug.cgi?id=376595
--- Comment #15 from Aetf <7437...@gmail.com> --- Okay. So setting watch point itself seems normal in log. The crash actually happens before the watch point was triggered. gdb returned two replies for 35-exec-continue command: 35^running and 35^error,msg=\"Command aborted.\" This doesn't confirm to the spec and confused kdevelop which assumes each reply must have a corresponding command. I will fix this by ignoring wild replies from gdb. Please try if my patch fixes the crash. But this is likely also a bug within gdb itself. I would suggest verify if debugging directly in gdb command line works with your program if there's still something wrong. (Probably something like the program doesn't resume execution because the exec-continue command failed) -- You are receiving this mail because: You are watching all bug changes.
