Tag: app-subdomain-redirection:code-blocks

So you’ve created and debugged your first program in Code::Blocks. But something’s still not working right. What do you do next? Let’s go over some common problems that many programmers run into when getting started with Code::Blocks. We will also review frequently used troubleshooting suggestions and tips.

Common issues with Code::Blocks

I’m unable to build my project

Problem: All of the Build-related options are grayed out.

Solution: Code::Blocks checks the file extension for individual files before allowing them to be compiled. Save your file with the correct file extension (*.c or *.cpp). More often it is useful to create a project so that Code::Blocks can manage the entire build.

I’m unable to compile my project

Problem: Syntax. Syntax errors, incorrect errors in formatting of code, and accidental typographical errors will not allow the program to run correctly. You may see errors that do not allow you to build or compile.

Solution: Methodically check the syntax of the programming language that you are using. You can do this by reading your code. You can step through your code line by line, or you may choose to set break points and watches to isolate segments of your code. If needed, consult documentation for the specific programming language that you are using. Sometimes the smallest error can disable an entire program.

Multiple undefined reference errors

Problem: Every time I build, Code::Blocks reports multiple undefined reference errors. Example:
undefined reference to `WSACleanup@8
undefined reference to `WSACleanup@0
Solution: Check to see if the required library is not linked with your project. Go to Project->Build options…->Linker settings (tab) and add the required library or libraries.

If the error includes a line number, it is likely that this is a problem with your code. Track down your function declarations and implementations. Ensure they all match up, are spelled correctly, and have the correct scope resolution.

A Code::Blocks option I expect to be able to find is missing

Problem: The option I was looking for is nowhere to be found in Code::Blocks.

Solution: Many features of Code::Blocks are implemented by means of plugins. Open Plugins->Manage plugins… and ensure that the one you are trying to use is not disabled. If the plugin you are looking for is not in the list, it’s possible that you removed or disabled it on installation. To acquire the plugin, reinstall Code::Blocks (double checking that the desired plugin is included).

These are some of the most common errors that you may run into when using Code::Blocks. To learn about other errors or problems, consider checking http://stackoverflow.com or https://en.wikipedia.org/wiki/Code::Blocks. In addition, when using any software program, app or utility, it’s always a good idea to familiarize yourself with the documentation on the developer’s website. Further documentation is available at http://www.codeblocks.org/.

You are now well on your way to building and managing complex programs and applications using the complete and extendable Code::Blocks IDE.

________________

Sources:
http://www.codeblocks.org/
https://en.wikipedia.org/wiki/Code::Blocks
http://stackoverflow.com

More:

Download Code::Blocks

So, you’ve successfully created your first program in Code::Blocks – that is, you have written your source code, made any changes needed, and compiled and built your code. Maybe you got lucky and your program came out just right on the first try. But more likely you’ll need to make edits and debug your code in order to come out with a finished product that works properly.

So let’s learn how to debug in Code::Blocks, which is a popular IDE that many developers use to create code with C/C++ and other languages.

How to debug your program

Debugging your program in Code::Blocks might seem daunting at first, but after we review the process it will become second nature. The process of debugging involves tracing the program operation step by step. You also use the debugging process to place breakpoints where you wish the program to pause. A debugger can pause your program and you can watch the values of the variables that you have defined. This will help you to isolate errors or mistakes in the code. First, let’s talk about using breakpoints.

Using breakpoints

1. Set a place in the code to have the program pause. To do this, pull down the Debug and click Run to cursor. The cursor should be over the first line of code where you plan to start the tracing process. 
2. Move the cursor over the line where you want your program to stop. This is called a breakpoint. Now you can tell the debugger to run the program up to the cursor’s position, or line number. This allows you to see the point where your program malfunctions.

When the debugger detects a breakpoint, the program pauses and the debugger allows you to inspect your code. The breakpoint remains until you remove it. It can be toggled on and off by pressing F5. (Prior to running the program in debug mode, breakpoints will be marked with a red circle. )

Problematic areas of code can now be isolated between breakpoints for easier identification.

Using watches to monitor code variables

To monitor specific variables during the execution of the program, you should open the Watches window. This will highlight the variables in your code.

Do this by going to the Debug pull-down menu. Click Debugging Windows and then Watches. The Watches menu shows a list of the variables in your code. If nothing is next to the listed variable, there is currently nothing assigned to it in the program.

Debug tips

Yellow markers are displayed on the left side of the screen beside the location of breakpoints in the code when the running program has paused. This lets you see the exact location of the breakpoint.

To advance to next line of code, select Next line from the Debug menu. You can also use the F7 key as a keyboard shortcut to accomplish the same task. This allows you to walk through your code line by line in search of errors. This reduces troubleshooting time greatly.

When you are finished debugging, click Continue, and your program will run to the end. If your program is stuck and will not advance, you have the option to choose Stop debugging from the Debug menu.
When you run the debug process, the yellow triangle will show you where the breakpoint has stopped the program from running. The red circle will show the various locations that the breakpoints have been placed throughout the code.

Now that you understand the basics of debugging in Code::Blocks, you are on your way to completion of a successful program. When you have completed the debugging process Code::Blocks will ask you if you want to save your workspace. If so, click yes; it is now safe to exit the program.

Sources:

http://www.codeblocks.org/

http://www.sci.brooklyn.cuny.edu/~goetz/codeblocks/codeblocks-instructions.pdf

https://en.wikipedia.org/wiki/Code::Blocks

Related links:

Download Code::Blocks

If you’re new to Code::Blocks IDE and you’ve already downloaded and installed the program, it’s a good time to create your first program. We’ll  go over the steps to create a specific starter program using Code::Blocks and programming in C++. This is a great way to get familiar with the layout and workings of the software.

Add files to your project

Follow these steps to add files:

1. Go to the Project menu and select Add files. This will bring in the files associated with your program.
2. Add any additional .cpp or header files to your project at this step.
3. Name your files. Now you will see your main .cpp file (if programming in C++) as well as any other .cpp files that you have added to your project. Press Select All to have this file saved as both debug & release targets. Press OK when done.

Edit your files

1. To begin to edit a file from your project, double-click the file name from sources, and it will appear in the window with line numbers.
2. Write your code in the main.cpp file (or alternate .cpp file that you have chosen.)
3. When testing your code, make sure that Debug is selected as the target to use. This is needed to have a debug version available once you compile your code.

Syntax

In C++ there is no special syntax for streaming data input or output. Instead, these are combined as a library of functions. Iostream provides basic input and output services for C++ programs; it must be included for your program to function properly. This is why we must include the #include< Iostream> line in our program.

We also must include the #include <cstdlib> to the program in C++ .
Be sure the statements you wish to print in the console are between “” quotation marks. For example:

cout << “Hello there!….or should I say NAMASTE “<<endl;

Be sure to use correct beginning and ending statements with each line of code. For basic C++ syntax please see this link.

Input the following code into your project (see the image above for comparison):

#include <iostream>
#include <cstdlib> //wxDev-C++ users may need this header file here to allow calls to system commands

using namespace std;

int main()
{
cout << “Hello there!….or should I say NAMASTE “<<endl;
cout << “Looks like it is going to be another warm summer day “<<endl;
cout << endl;
cout << “Time to get to the Maggini Hall labs where it is cool\n”
<< “and write some useful computer programs”<<endl<<endl;
cout << “C++ is a high-level programming language”;
cout << “…..LETS GIVE IT A GO!!!”<<endl;
cout << “your name here”<<endl;
// system (“PAUSE”); //if using MS Visual C++…not needed in Code::Blocks or XCode
return 0;

}

Then save your work.

Compiling

After you complete the writing and editing of your program, you must compile the file. To do this, first go to the Build menu and select Compile Current File (or Ctrl+Shift+F9).

Next, test your project. From the Build pull-down menu, click Build and Run. This step will build an executable file for you. A project build takes the compiled versions of your source files and combines them into one single program. Your program output will now be displayed. You will see all of the text you wrote in between the quotes displayed as program output.

If an error is displayed, check the syntax of your code and check for missing pieces, or unintentional errors.

Although this is a very simple program, it is the foundation for beginning to write more in-depth programs in Code::Blocks. As your programs increase in length and depth, the same basic steps apply. Happy programming!

Sources:
https://www.cprogramming.com/tutorial/lesson1.html

https://en.wikipedia.org/wiki/Code::Blocks