After some problems which occured with the VisualC-port of C::B yesterday, i became suspicious, if these problems were only VC-related or "home-brewed" in the code and (if so) they must also appear in the gcc-build of C::B if using the wx-debug-dll.
Therefore i did a C::B build using the wxWidgets-2.6.1 debug-dll - and there are similar (but not exactly the same) 
wxWidgets Debug Alerts, some of them posted here with their (frequency):
- Thaw() without matching Freeze()          (*** very often)
 - wxYield called recursively                       (**   often)
 - EM_STREAMIN didn't send EN_UPDATE   (*     rare)
 - wxMenu::Check: no such item                (oo   never ending chain, triggered continously)
 
has anybody already looked at this phenomena ?
i think, we should use the wxWidgets-Debug-build in order to find and lastly correct more flaws in the code, isn't it ?
any thoughts about ?