User forums > Help

crash when use wxsmith

<< < (2/6) > >>

stahta01:
I am building wxWidgets 3.0.2 32 bit right now; in a several hours, I plan to see if I get the problem under Windows 10 32 bit.

Edit: Note to self, need both wxSmith and wxSmith MIME plugins enabled to do testing.

Tim S.

stahta01:
Duplicated the crash on Windows 10 32 bit.
Now going to use debug wxWidgets to see if more info results during crash.

Edit:

--- Code: ---gcc version 5.1.0 (tdm-1)

--- End code ---

Tim S.

stahta01:
Attaching crash report; it crashed twice.

Edit: Using wxWidgets 3.0.2 with patch on it to build using GCC 6.3.0.
Edit2: Now building wxWidgets WX_3_0_BRANCH to see if the problem has been fixed in that git branch.
Edit3: Problem NOT fixed in WX_3_0_BRANCH git branch; so, likely NOT wxWidgets problem.
Going to build using MinGW64 GCC 6.3.0 and see if problem goes away; I am better using GDB under MSys2.
Note: I still am very bad at using gdb, I just might be able to do a back trace under MSys2.

Tim S.

oBFusCATed:
Can you post a backtrace/callstack from the debugger. This report is hardly readable...

skool daze:

--- Quote from: BlueHazzard on April 19, 2017, 04:18:23 pm ---You probably have to recompile codeblocks with the debugger symbols enabled so the backtrace is filled with readable function names:
In Settings->Global Variables->cb_release_type->base add a "-g"
then you have to rebuild all codeblocks:
Build->Rebuild workspace

--- End quote ---
For rebuild/recompile do you mean compile+link C::B from sources or is because  icequan says "the codeblocks built against wx30"?

Navigation

[0] Message Index

[#] Next page

[*] Previous page