Code::Blocks Forums

User forums => Help => Topic started by: BickeringNut on March 12, 2013, 08:34:35 pm

Title: Force Close MACBOOK PRO
Post by: BickeringNut on March 12, 2013, 08:34:35 pm
Hi,
I used to use codeblocks v 10 fine with no issues. I recently upgraded codeblocks v12. something and now when I open a document Codeblocks force closes on me within seconds. I unistalled codeblocks and reinstalled it and the same thing happens. I installed the newest version of Xcode prior to updated codeblocks. I am going to use codeblocks to write code in C++. I am running the newest version of Mac OS. Any help would be greatly appreciated.
Title: Re: Force Close MACBOOK PRO
Post by: Jenna on March 12, 2013, 08:53:05 pm
One of these threads might be helpful:
http://forums.codeblocks.org/index.php/topic,17325.msg118870.html#msg118870 (http://forums.codeblocks.org/index.php/topic,17325.msg118870.html#msg118870)
http://forums.codeblocks.org/index.php/topic,17279.msg118556.html#msg118556 (http://forums.codeblocks.org/index.php/topic,17279.msg118556.html#msg118556)
http://forums.codeblocks.org/index.php/topic,17238.msg118247.html#msg118247 (http://forums.codeblocks.org/index.php/topic,17238.msg118247.html#msg118247)
Title: Re: Force Close MACBOOK PRO
Post by: BickeringNut on March 14, 2013, 12:34:38 am
Thanks a lot. The first linked help me but now every time I try to create a . cpp file and run it it shows up as "No such file or directory". Any idea?
Title: Re: Force Close MACBOOK PRO
Post by: Jenna on March 14, 2013, 07:06:32 am
Thanks a lot. The first linked help me but now every time I try to create a . cpp file and run it it shows up as "No such file or directory". Any idea?
Please post the exact error message (in code-tags) and the exact steps you did to trigger this issue
Title: Re: Force Close MACBOOK PRO
Post by: BickeringNut on March 15, 2013, 05:51:04 am
I open a file and when I build it it does not show as any errors are there. Then I run it and my terminal pops up and shows me the directory the file is in and then states "No such file or directory." There is not much more I can explain about this issue.