Code Blocks stops working when Watches windows is opened

[julramos]

Hi everyone!

I've been using Code Blocks for some time now and never had any problem like this. I'm trying to debug a project and it runs and compiles smoothly, but when I open the watches window the Code Blocks get really unstable, in a point that it crashes when I move the mouse over the watches window. 

I don't know what is happening cause it works well in other projects. I think it may be related to the fact that I'm using global variables in this project (although there are other projects with global variables that function normally), is there some particularly correct way to watch global variables?

Thanks for the attention!

[oBFusCATed]

What version and os are you using?
Are these global variables arrays/vectors or other complex structures?

[julramos]

Sorry for not mentioning it!
I'm using Windows 7 64 bits and Code Blocks 13.12 with GNU GCC Compiler.
The global variables include vectors and complex structures. I didn't know it mattered 
Should I not implement them as global variables?
Thanks for the attention!

[julramos]

I've just turned all the global variables into local variables and the problem persists.
It doesn't make any sense cause it only happens with this specific project. 

[BlueHazzard]

Can you post a example class that is causing the problem? Probably it is some parser error from the gdb output.... global or not has nothing to do with this, only the structure of your variables...

greetings

[oBFusCATed]

If you're breaking before the c-tor for these vectors has run and you have python pretty printers enabled in your gdb, then you'll see exactly this behaviour.