Author Topic: C:B build using wx261_debug_dll  (Read 5953 times)

Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
C:B build using wx261_debug_dll
« on: September 28, 2005, 08:26:35 am »
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 ?

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: C:B build using wx261_debug_dll
« Reply #1 on: September 28, 2005, 08:32:20 am »
That's what's keeping RC2 from being released. I want to build codeblocks with debug wx to fix those (hoping to find the time this weekend)...
Be patient!
This bug will be fixed soon...

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Re: C:B build using wx261_debug_dll
« Reply #2 on: September 28, 2005, 11:55:44 pm »
The thaw could be solved by making a derivative of the object in question, and add a "freezecounter". If it's 0, don't do nothing.

Perhaps you could make a Freezer class, which has the counter. The class will have only ONE object, the wxwindow in question that you want to freeze / thaw. (Or something).

The recursive wxyield is one i've been ranting for ages. Setting the "extra stability" in environment options solves it.

The EM_STREAMIN O.o I don't know about.

Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
Re: C:B build using wx261_debug_dll
« Reply #3 on: October 13, 2005, 12:42:09 pm »
i have done a patch which addresses the
  • Thaw() without matching Freeze()
  • wxYield called recursively
topics.

but i've read in this thread
http://forums.codeblocks.org/index.php/topic,854.msg5932.html#msg5932
that Yiannis is suspicious against.

Yiannis you maybe want to have a look about this patch doesn't mess something,
therefore i post it here instead of committing to cvs.

regards
tiwag

[attachment deleted by admin]

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: C:B build using wx261_debug_dll
« Reply #4 on: October 13, 2005, 12:56:20 pm »
Have you tested it with wx2.4 and wx2.6?
Be patient!
This bug will be fixed soon...

Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
Re: C:B build using wx261_debug_dll
« Reply #5 on: October 13, 2005, 01:06:17 pm »
i have tested with wx2.6.1 and 2.6.2 , don't have a wx2.4.2 setup at this time available

what are the special needs for wx242 when using freeze ?

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: C:B build using wx261_debug_dll
« Reply #6 on: October 13, 2005, 02:27:36 pm »
I don't recall now. Only that it behaved differently...
Never mind, I 'll test it.
Be patient!
This bug will be fixed soon...