News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

Code blocks crashes on start up

Started by keniff, October 11, 2009, 09:03:24 PM

Previous topic - Next topic

keniff

Hello all,
I had Code::blocks 8.02 running on my windows xp home pc for some time. After i tried to install the OpenFrameworksWizard i can't start up codeblocks anymore. I followed this tutorial:
http://code.google.com/p/ofcodeblocks/wiki/InstallingOpenFrameworksWizard
After step 3 i had to restart code::blocks but it kept crashing, or better put, i wouldn't start up. Starting up my process manager i noticed that codeblocks.exe was using over 500MB of RAM and using alot of my CPU. No matter how long i waited, it wouldn't start up the program, nor give a windows crash report. It was just idling at 500MB it seemed.

After uninstalling and reinstalling several times i keep having the same problem. I uninstalled properly, cleaning out my registry. I downloaded the latest version. I downloaded the latest mingwm10.dll. But to no avail.

I do have a crash report in my Codeblocks folder, stating the following:

-------------------

Error occured on Sunday, October 11, 2009 at 20:39:14.

C:\Program Files\CodeBlocks\codeblocks.exe caused an Access Violation at location 6190ad05 in module C:\Program Files\CodeBlocks\codeblocks.dll Reading from location 00000004.

Registers:
eax=00000000 ebx=00000002 ecx=42c90020 edx=033fff98 esi=00c75458 edi=0023feb8
eip=6190ad05 esp=0023f650 ebp=0023f7d8 iopl=0         nv up ei pl nz na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010202

Call stack:
6190AD05  C:\Program Files\CodeBlocks\codeblocks.dll:6190AD05  _ZN4SQVM7ExecuteER11SQObjectPtriiiS1_jNS_13ExecutionTypeE
6190E022  C:\Program Files\CodeBlocks\codeblocks.dll:6190E022  _ZN4SQVM4CallER11SQObjectPtriiS1_j
618FAD2E  C:\Program Files\CodeBlocks\codeblocks.dll:618FAD2E  sq_call
63C35700  C:\Program Files\CodeBlocks\share\codeblocks\plugins\scriptedwizard.dll:63C35700  _ZN14cbWizardPlugin9BuildMenuEP9wxMenuBar
63C1683D  C:\Program Files\CodeBlocks\share\codeblocks\plugins\scriptedwizard.dll:63C1683D
617D7A0C  C:\Program Files\CodeBlocks\codeblocks.dll:617D7A0C  _ZN8cbPlugin6AttachEv
61866800  C:\Program Files\CodeBlocks\codeblocks.dll:61866800  _ZN13PluginManager12AttachPluginEP8cbPluginb
61866D56  C:\Program Files\CodeBlocks\codeblocks.dll:61866D56  _ZN13PluginManager14LoadAllPluginsEv
004341F6  C:\Program Files\CodeBlocks\codeblocks.exe:004341F6
00438B13  C:\Program Files\CodeBlocks\codeblocks.exe:00438B13
004042A0  C:\Program Files\CodeBlocks\codeblocks.exe:004042A0
00405443  C:\Program Files\CodeBlocks\codeblocks.exe:00405443
00453E58  C:\Program Files\CodeBlocks\codeblocks.exe:00453E58  _ZN12cbToolPlugin9BuildMenuEP9wxMenuBar
6CC7708A  C:\Program Files\CodeBlocks\wxmsw28u_gcc_cb.dll:6CC7708ADwarf Error: found dwarf version '16896', this reader only handles version 2 information.  _Z12wxInitializeiPPw
6CCD21B8  C:\Program Files\CodeBlocks\wxmsw28u_gcc_cb.dll:6CCD21B8  _Z7wxEntryP11HINSTANCE__S0_Pci
00405CDE  C:\Program Files\CodeBlocks\codeblocks.exe:00405CDE
0044DFD8  C:\Program Files\CodeBlocks\codeblocks.exe:0044DFD8
0040124B  C:\Program Files\CodeBlocks\codeblocks.exe:0040124B
004012B8  C:\Program Files\CodeBlocks\codeblocks.exe:004012B8
7C7E7077  C:\WINDOWS\system32\kernel32.dll:7C7E7077  RegisterWaitForInputIdle


I have no idea what this is supposed to point out. Can somebody please help me out ?

Jenna

If the changed config.script causes the crash on startup, or any other change to C::B's configuration, it will not be corrected by uninstalling or reinstalling the software.
The registry is only used for the file-associations, so there is no need to change anything.

The configuration-files (also the changed config.script) are saved in %APPDATA%\codeblocks.
If you delete the whole directory, all your global changes you made to C::B are lost (search-directories, toolchain, ...).

As start-point, you should delete (or rename) %APPDATA%\codeblocks\templates\wizard\config.script.
If that works, you either messed something up there, or the OpenFrameworksWizard-script makes C::B crash.

If that does not work, you can try to rename the whole conf-folder and start C::B. It will create new files with default-values.

keniff

thank you very much for the reply Jens  :D

I located the appdata folder and deleted the default.conf and lo and behold, i'm back in the running!