User forums > General (but related to Code::Blocks)

wxWidgets 3.1.5

<< < (2/7) > >>

Miguel Gimenez:
Can you attach a stack trace?

oBFusCATed:
Have you tried to reproduce this in wx-samples? Does the choice (widgets probably) sample works correctly with your build?

gd_on:
@ Miguel : There is no RPT file produced, but I don't think it's what you want. How do you produce a stack trace ? Is it necessary to have a debug version of C::B ?
@ oBFusCATed : I don't have any (such) messages in  any samples I tried. Particularly, I tried "choice" in "wxwidgets" sample and it seems to work as it should.

oBFusCATed:
You need a debugger and possibly symbols. No need to build non-optimized builds.

gd_on:
OK, solved.
I have added DEBUG_FLAG=0 in my command line to build wxwidgets.
Until now, I had DEBUG_LEVEL=0. I have seen that somewhere, some time ago and until now I had no problems. But the parameter in the command line is DEBUG_FLAG, which is 1 by default and set a wxDEBUG_LEVEL (not DEBUG_LEVEL). Now, with DEBUG_FLAG=0, it forces wxDEBUG_LEVEL to 0, and I am no more annoyed by this wxAssert Message. May be, it masks an other problem, but it works as in 3.1.4 version.

Navigation

[0] Message Index

[#] Next page

[*] Previous page