User forums > Help
Can Not Run Nightly Build
Mr. Awesome:
Well, that same problem has cropped up again, strangely enough. Just a few minutes ago, I started up CodeBlocks and was greeted with the same messages. So, I deleted the codeblocks subdirectory in AppData and restarted CodeBlocks, to find out that magically it was working again. Suspicious, I restored the old default.conf file in the codeblocks subdirectory and found CB to be broken again.
There is something wrong with the old configuration file, but I kind of need it as it has all my settings in it (obviously). Not only do I really not want to input all of my settings for the FOURTH time, but I want to make sure any future CB config files don't become corrupted again.
The error messages were:
Error: C:\Documents and Settings\Owner\Application Data\codeblocks\default.workspace does not exist...
And the standard Windows error "codeblocks.exe has encountered a problem and needs to close." Where you can send an error report to MS.
Here is the default.conf file:
http://www.geocities.com/erichof425/default.xml
TDragon:
Without reading your config file, I know there is (or at least there used to be) a bug with loading the default workspace at startup; the workaround I use is to instead load a blank workspace. Find the line in your default.conf file that reads "<BLANK_WORKSPACE bool="0" />" and change it to "<BLANK_WORKSPACE bool="1" /> to fix this. (And don't choose "Open default workspace" on application start-up until you know it's fixed.)
Mr. Awesome:
Thanks, now the problem is solved permanently. :D
Michael:
--- Quote from: TDragon on February 01, 2006, 12:27:46 am ---Without reading your config file, I know there is (or at least there used to be) a bug with loading the default workspace at startup; the workaround I use is to instead load a blank workspace. Find the line in your default.conf file that reads "<BLANK_WORKSPACE bool="0" />" and change it to "<BLANK_WORKSPACE bool="1" /> to fix this. (And don't choose "Open default workspace" on application start-up until you know it's fixed.)
--- End quote ---
Hello,
Did you have already submitted this bug(s) to sourceforge?
Best wishes,
Michael
TDragon:
I haven't yet. When I first noticed it, I assumed it was a temporary artifact of someone's SVN changes and would be fixed soon. If it still isn't, I can submit a bug to the tracker today.
Navigation
[0] Message Index
[*] Previous page
Go to full version