I am also seeing some problems with watch variables. You risk a crash if a variable goes out of scope. In addition, if you stopped debugging with variables still in the watch window, and then start debugging again, the IDE can crash. SIGSEGV.

Which type of variable did you watch?

GDB has no idea (little idea) about the scope of a variable.

Can you give some sample code?

It crashes on any variable.

when I remove a watch-variable in the watchwindow while C::B is retrieving the value from gdb it crashes in the moment gdb is ready.

I guess C::B has a reference to the watch-variable and the reference isn't valid when gdb print out the value and C::B tries to write into the variable.

Hope this helps ?

This bug is now fixed in HEAD.

Thank you for reporting it.