Recent Posts

Pages: 1 2 [3] 4 5 6 7 8 ... 10
Help / Re: C::B 17.42 Windows 10 and 7, hangs on build, cannot abort have to terminate
« Last post by jspang on November 10, 2019, 04:53:29 am »
Well OK, it is the original poster here again with an update.

So I worked out the cause. My simple program opens a console, which pops up and remains open at the end of execution. If the program compiles OK and I close the console window at completion of the test, control passes back to my editing window just fine and the 'build and run' button activates again. Everything is fine.

However, if I happen to click on the editor window BEFORE I close the console window, the console window disappears I-don't-know-where, but it would seem it stays open. I cannot find it again. Because the console is not killed, the compiler is still running. I can't get the console back (to kill it), and the compiler abort button does not work (this seems like a C::B bug to me).

So the combination of me not realizing what I had done and the abort button not working led me to this confusing (to me) problem, as a fairly new C::B user. Probably someone who has figured out the things to avoid might shrug and say its my fault, but TBH it seems like flaky operation to me. The abort button should do what it says.

For now, I know what not to do with the C::B gui. Take this as a bug/report suggestion for improvement as you see fit.

Help / C::B 17.42 Windows 10 and 7, hangs on build, cannot abort have to terminate
« Last post by jspang on November 10, 2019, 04:25:27 am »

I have fresh installations of C::B with mingw using the default gcc compiler, standard installations of binaries running on two different computers, one win 10 and the other windows 7 pro build 7601 sp 1. Both experience the same problems on fairly trivial code compile/run attempts.

Basically, executing "Build and Run" the build hangs, the 'red X' abort button has no effect on the build, the entire C::B program seems to hang up. It happens on both machines on different user application code. There is nothing really in common between the machines. These are first time installs of CB so there are no old libraries hanging around etc.

I am able to run some simple code fine, but editing and compiling along the way with the "build and compile" button seems to result in frequent hang-ups. On other occasions it works. It is possible that there is a bug in the code being compiled. It's hard to put a finger on the exact behaviour at this point. It seems like just running build without run might be more stable.

The causes of the hang seem to be varied and somewhat arbitrary, but perhaps loosly associated with code with a bug in it. On other occasions, it reports the bugs just fine and stops compiling by itself as expected. The project directory seems clean and tidy.

Could not see anything relevant in the fora.

Once it hangs, oddly some C:B menus work but the build buttons are greyed out, and attempting to kill the C::B window shell is not even possible. It complains that the compiler is still running and do I want to abort it. Saying yes it returns to hanging. Trying to kill the window again (right top X) finally asks if I want to kill the process. I can then restart. I am not sure yet if the error is directly repeatable, it could be. As mentioned, the compile abort button is ineffective at aborting the compile, even after a long wait.

I have managed to create a C++ application that crashes, and it seems to handle that properly.

Any guidance greatly appreciated thanks.
Help / Re: Blank window after running program
« Last post by sanch0 on November 09, 2019, 08:05:26 pm »
Yes, you were right. Just like I thought. I added every single .exe file from CodeBlocks to anti-virus exceptions list and now it works.
Help / Blank window after running program
« Last post by sanch0 on November 09, 2019, 01:12:54 pm »
Hey guys,
I have problem with my CodeBlocks. I downloaded program from official site (with compiler, mingw). After installation I tried to check if everything is OK, but it isn't. After building and running very basic code there is blank window and I can't even close it. I have to use Task Manager to close it. You can look at it, there's attachment.

Moreover, CodeBlocks asks me after creating new project something like this: "Select the targets file should belong to" and there is Debugger and Release option. On tutorials I haven't seen window like this yet.

Please, help me :/
Development / Re: A possible bug in 'cbproject.cpp'
« Last post by oBFusCATed on November 09, 2019, 01:06:01 pm »
Fixed in svn... Lets see how many projects I've broken.  ::)
Help / Re: CodeBlocks Troubleshooting: Reading file line by line
« Last post by stahta01 on November 09, 2019, 02:15:31 am »
My wild guess is you need an terminal program installed or you need to tell Code::Blocks what terminal program to use.

Edit: Look to see what terminal it is trying to use under
Setting -> Eviroment
General Setting
Check the value of "Terminal to launch console programs"

Tim S.
Help / Re: CodeBlocks Troubleshooting: Reading file line by line
« Last post by hidefromkgb on November 08, 2019, 09:22:13 pm »
Well… This is not a programming forum.
The more appropriate place to ask your question is e.g. here.
Nevertheless, please show us the code, for I`m sure your problem is easy to solve.
Using Code::Blocks / Re: [SOLVED] 'AM_OPTIONS_WXCONFIG' not found in library
« Last post by hidefromkgb on November 08, 2019, 09:07:25 pm »
Okay, I`m ready to help!
This is the article to be edited, I presume?
The problem is, in Arch there is actually no need to compile C::B from source anymore unless you want the latest features right now, e.g. like I do.
Can I change the name of the article to something more general, e.g. «Installing Code::Blocks on Arch Linux» to include the easy method of pacman -S codeblocks?
Help / CodeBlocks Troubleshooting: Reading file line by line
« Last post by clinthof on November 08, 2019, 08:02:23 pm »
Hey all,
I have written a C program in codeblocks to read a specified file line by line.  However, this is the output I get:

/private/var/folders/01/93nfj2q543q6ctr7hjs04vfw0000gn/T/AppTranslocation/7CB58FA2-56DE-4E40-9080-8DB0187CF55A/d/ DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:. /Users/MYNAME/Desktop/readLbyL/bin/Debug/readLbyL
myCP:~ MYNAME$ /private/var/folders/01/93nfj2q543q6ctr7hjs04vfw0000gn/T/AppTranslocation/7CB58FA2-56DE-4E40-9080-8DB0187CF55A/d/ DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:. /Users/MYNAME/Desktop/readLbyL/bin/Debug/readLbyL

What is causing this? Thank you!
Pages: 1 2 [3] 4 5 6 7 8 ... 10