Author Topic: build codeblocks with wxWidgets3.1.0  (Read 6090 times)

Offline icequan233

  • Multiple posting newcomer
  • *
  • Posts: 31
build codeblocks with wxWidgets3.1.0
« on: February 27, 2017, 10:10:01 am »
       hi,guys.I was trying to build codeblocks with wxWidgets3.1.0 on win10,I build it successfully,but when I launch the codeblocks,it shows as this picture..
       I don't know the reasons why it stops working,maybe is the OS'problem.Anyone has ideas or suggestion? Thanks.
       BTW,before building codeblocks,I disable many plugins unnecessary,but it looks like no useful.

Offline BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 3353
Re: build codeblocks with wxWidgets3.1.0
« Reply #1 on: February 27, 2017, 10:59:46 am »
There should be a codeblocks.rtp file in the same directory as the codeblocks.exe.

Can you post the content here within code tags? (the # symbol in the new post editor)

Also have you run update30.bat?

Offline icequan233

  • Multiple posting newcomer
  • *
  • Posts: 31
Re: build codeblocks with wxWidgets3.1.0
« Reply #2 on: February 27, 2017, 12:22:46 pm »
Thanks.
Code
Error occured on Saturday, February 25, 2017 at 21:21:13.

codeblocks.exe caused an Access Violation at location 66A9EC43 in module wxmsw310u_gcc_custom.dll Reading from location 00000010.

Registers:
eax=00000000 ebx=66eabb94 ecx=00000000 edx=00000000 esi=66ebc1c4 edi=66e8a4cc
eip=66a9ec43 esp=008af290 ebp=06f81da0 iopl=0         nv up ei pl zr na po nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00210246

AddrPC   Params
66A9EC43 06F81DA0 00000002 00000000  wxmsw310u_gcc_custom.dll!wxXmlDocument::Save

codeblocks.exe 16.1.0.0
ntdll.dll    10.0.14393.479
KERNEL32.DLL 10.0.14393.0
KERNELBASE.dll 10.0.14393.479
msvcrt.dll  7.0.14393.0
SHELL32.DLL 10.0.14393.693
COMCTL32.DLL 6.10.14393.447
cfgmgr32.dll 10.0.14393.0
combase.dll 10.0.14393.576
ucrtbase.dll 10.0.14393.0
windows.storage.dll 10.0.14393.479
powrprof.dll 10.0.14393.0
RPCRT4.dll  10.0.14393.82
SspiCli.dll 10.0.14393.576
advapi32.dll 10.0.14393.0
sechost.dll 10.0.14393.0
shlwapi.dll 10.0.14393.0
CRYPTBASE.dll 10.0.14393.0
bcryptPrimitives.dll 10.0.14393.0
GDI32.dll    10.0.14393.206
gdi32full.dll 10.0.14393.576
USER32.dll  10.0.14393.576
win32u.dll  10.0.14393.51
kernel.appcore.dll 10.0.14393.0
shcore.dll  10.0.14393.0
profapi.dll 10.0.14393.0
SHFOLDER.DLL 10.0.14393.0
wxmsw310u_gcc_custom.dll 3.1.0.0
codeblocks.dll
COMDLG32.DLL 10.0.14393.479
exchndl.dll 0.8.0.0
OLE32.dll    10.0.14393.576
PSAPI.DLL    10.0.14393.0
OLEAUT32.DLL 10.0.14393.447
msvcp_win.dll 10.0.14393.0
mgwhelp.dll 0.8.0.0
dbghelp.dll 6.3.9600.17029
VERSION.dll 10.0.14393.0
WINMM.DLL    10.0.14393.0
WSOCK32.DLL 10.0.14393.0
WINSPOOL.DRV 10.0.14393.0
WS2_32.dll  10.0.14393.206
WINMMBASE.dll 10.0.14393.0
bcrypt.dll  10.0.14393.576
IMM32.DLL    10.0.14393.0
uxtheme.dll 10.0.14393.0
MSCTF.dll    10.0.14393.479
dwmapi.dll  10.0.14393.206
MMHook.DLL  0.9.1.2243
mpr.dll      10.0.14393.0
clbcatq.dll 2001.12.10941.16384
dataexchange.dll 10.0.14393.206
dcomp.dll    10.0.14393.0
d3d11.dll    10.0.14393.479
dxgi.dll    10.0.14393.479
twinapi.appcore.dll 10.0.14393.206
WindowsCodecs.dll 10.0.14393.576
msftedit.DLL 10.0.14393.206
Windows.Globalization.dll 10.0.14393.447
Bcp47Langs.dll 10.0.14393.0
globinputhost.dll 10.0.14393.0
abbreviations.dll
Astyle.dll
autosave.dll
classwizard.dll
codecompletion.dll
compiler.dll
debugger.dll
defaultmimehandler.dll
OccurrencesHighlighting.dll
openfileslist.dll
projectsimporter.dll
scriptedwizard.dll
todo.dll
xpmanifest.dll
msimg32.dll 10.0.14393.0
WININET.dll 11.0.14393.479
iertutil.dll 11.0.14393.447
ondemandconnroutehelper.dll 10.0.14393.0
IPHLPAPI.DLL 10.0.14393.0
winhttp.dll 10.0.14393.351
mswsock.dll 10.0.14393.0
NSI.dll      10.0.14393.0
WINNSI.DLL  10.0.14393.0
DNSAPI.dll  10.0.14393.206
urlmon.dll  11.0.14393.479

Windows 10.0.14393
DrMingw 0.8.0
Of course,I ran the update30.

Offline BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 3353
Re: build codeblocks with wxWidgets3.1.0
« Reply #3 on: February 27, 2017, 12:29:16 pm »
No debug information...

Have you a other installation of codeblocks around?
Can you start codeblocks with the parameter "--debug-log --multiple-instance --verbose -p debug"?
Can you run codeblocks trough the debugger?
Can you recompile codeblocks with debug symbols enabled (using the global variable cb_release_type and add a -g there, if you use codeblocks to compile)?

Offline icequan233

  • Multiple posting newcomer
  • *
  • Posts: 31
Re: build codeblocks with wxWidgets3.1.0
« Reply #4 on: February 27, 2017, 01:20:24 pm »

I was debugging the codeblocks right now,but I also have this problem.my cb is still crash .Maybe it is the wx's bughttp://trac.wxwidgets.org/ticket/17483

Offline icequan233

  • Multiple posting newcomer
  • *
  • Posts: 31
Re: build codeblocks with wxWidgets3.1.0
« Reply #5 on: February 27, 2017, 03:13:45 pm »
      OK,it is the wx'bug indeed.see thishttp://trac.wxwidgets.org/changeset/aa3acfdd15eff1519a41b48a2babe4cba75660f9/git-wxWidgets
      And I rebuild cb,now I can open the codeblocks correctly,no crash.thanks,BlueHazzard.

Online ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5906
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: build codeblocks with wxWidgets3.1.0
« Reply #6 on: February 27, 2017, 04:05:29 pm »
      OK,it is the wx'bug indeed.see thishttp://trac.wxwidgets.org/changeset/aa3acfdd15eff1519a41b48a2babe4cba75660f9/git-wxWidgets
      And I rebuild cb,now I can open the codeblocks correctly,no crash.thanks,BlueHazzard.

It is GCC's bug, not wx' bug.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: build codeblocks with wxWidgets3.1.0
« Reply #7 on: April 21, 2017, 02:33:28 pm »
It is GCC's bug, not wx' bug.
Please don't make such accusations without a thorough investigation!
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]