07-18-2013
Breakpoints dont work in Codeblocks, code does not build
Hey so I've written a program and it crashes every time I run it. I tried placing breakpoints to see what was going but to my surprise they do not work! I've placed them anywhere and they do not stop the execution of the program.
In fact if I add code and hit rebuild it doesn't even build that new code! I have a few outputs for debug placed before the old code (its new). When I either build or rebuild that new code doesn't display its data and the old code that comes after it does! Its like a new debug .exe isn't even being built.
8 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Alright.
My neighbor kid brings me his iBook and says nothing works. He decided to move the file system to his likeness and that semed to create the problems. Now he doesn't have access rights to his home.
I have run fsck over and over again and I keep getting ** fs modified **
I have also... (0 Replies)
Discussion started by: maxwell
0 Replies
2. Programming
Im unsure of how to clear break points using dbx v7.2.1
Ive tried using
delete linenumber of breakpoint
however this does not seem to work. Could anyone point me in the correct direction ?
regards (0 Replies)
Discussion started by: JamesGoh
0 Replies
3. UNIX for Advanced & Expert Users
Hi
I tried to put a cron job which pipes the logfile appended to date +%d
but it didnt work .
anyone know how to make this happen
thanks in advance
-prasad (7 Replies)
Discussion started by: p4cldba
7 Replies
4. Shell Programming and Scripting
Hallo,
I need to test a String (a special ip number-string).
So I want to run that:
ipadress=172.0.0.0
# for debugging:
echo $ipadress | egrep -e '172\.?\.??\.??$'
# the test that doesnt work
if test -z `echo $ipadress | egrep -e '172\.?\.??\.??$'` != ""
then
echo "match"
else... (1 Reply)
Discussion started by: wiseguy
1 Replies
5. Shell Programming and Scripting
Hi.
I´ve a script that should substitude the 8th line in a file called xxx.num6.
The "xxx" is set by an array filled with this command:
j=0
for Par in *.sys ; do
Par=`echo $Par | sed 's/\(.*\).sys/\1/'` ;
Par2="$Par" ; echo "${Par2}"
j=$((j + 1));
done
Now i try... (0 Replies)
Discussion started by: Lock3
0 Replies
6. UNIX for Dummies Questions & Answers
when i started booting linux ,after sometime both the mouse and the keyboard are getting freeze and wont respond(also the system gets hanged and all the process running dont go forward) ,nothing seem to work.
Keeping in mind that it will work after sometime ,i waited for one hour also ,but... (1 Reply)
Discussion started by: sanjay.login
1 Replies
7. Programming
Okay so I am just starting programming c++. I just started started to red "C++ for Dummies yesterday and theres a lot of things I do not understand from this book and this source code especially. I will first post the full source code and then post questions about certain thing, usually what they... (2 Replies)
Discussion started by: orszhak
2 Replies
8. Programming
hi all,
i have made a shell script and it runs until it reaches the if statement, doesn't the ! mean only if the command fails it will echo me that message and then exit
can anyone please help me what is wrong with my code?
many thanks,
rob
#!/bin/bash
echo "is this archive... (10 Replies)
Discussion started by: robertkwild
10 Replies
LEARN ABOUT CENTOS
cheatmake
CHEATMAKE(1) [FIXME: manual] CHEATMAKE(1)
NAME
cheatmake - fool make into not rebuilding certain files
SYNOPSIS
cheatmake [hidechangefile] [show] [whyfile]
DESCRIPTION
cheatmake is used to save time when recompiling. It can fool make into skipping files that haven't changed in a meaningful way. This can be
used for instance when you change a comment in a file but none of the actual code.
This utility is part of the KDE Software Development Kit.
OPTIONS
hidechange file
Hides the fact that file was changed by setting the timestamp into the past. Use with care!
show
Lists what files make currently needs to rebuild
why file
Explains why make must rebuild file
ENVIRONMENT
One of the following variables (but not both) should be set if the source directory is different from the build directory. If the build
directory is simply a subdirectory of the source directory, the simpler variable OBJ_SUBDIR should be used.
OBJ_SUBJDIR
Indicates that the build directory is in the given subdirectory of the source directory. For instance, if the source directory is
kdesdk and the build directory is kdesdk/obj-i386-linux, then OBJ_SUBDIR should be set to obj-i386-linux.
OBJ_REPLACEMENT
A sed expression that is used to transform the source directory into the build directory. For instance, if the source directory is
kdesdk/obj-i386-linux, then OBJ_REPLACEMENT should be set to s#kdesdk#kdesdk-obj#.
SEE ALSO
make(1)
AUTHORS
cheatmake was written by David Faure<faure@kde.org>. This manual page was prepared by Ben Burton<bab@debian.org> for the Debian
GNU/Linux(R) system (but may be used by others).
[FIXME: source] March 8, 2003 CHEATMAKE(1)