C::B breakpoints problem

[Kayl669]

Hey,

I've googled this issue (breakpoints are ignored in my Code Blocks installation) and it was suggested to someone that they download some kind of nightly build. I don't know what that is and was wandering if there was a way to fix my problem through settings changes or something less fundamental.

For any interested in helping (thx in advance) my setup is Ubuntu 9.10 with C::B 8.02. Is this some kind of debugger problem?

Thanks

[laserlight]

I never had an issue with breakpoints being ignored for Code::Blocks 8.02. You are using gdb, right? Which version is it?

(Oh, and I really wish that the Code::Blocks developers would just devote a month to get a arbitrarily chosen nightly tested more thoroughly for a new release.)

[Kayl669]

Hi again,

I'm using the GNU GCC compiler. Everything is as default because I'm very new to all this. Is GDB a compiler?
Thanks

[MK27]

gdb is a command line debugger.

There are several GUI frontends to gdb, eg see here:

http://cboard.cprogramming.com/progr...linux-ddd.html

However, altho it seems very awkward at first, I'd recommend finding a gdb tutorial and trying to use it on the command line for a while. Once you can remember a few simple commands (run, list, break, cont, print, backtrace) and understand the output, using gdb in terminal is pretty quick and easy, since you are compiling and testing in the terminal too:

[root~/C] gcc test.c
[root~/C] ./a.out
Segmentation fault
// damn, what'd I do this time?
[root~/C] gcc -g test.c   // use -g to compile with debugging symbols 
[root~/C] gdb ./a.out  // start gdb with the executable loaded 
(gdb) run
Starting program: /media/sda6/root/C/a.out 

Program received signal SIGSEGV, Segmentation fault.
memcpy () at ../sysdeps/x86_64/memcpy.S:91
91		movl	%ecx, (%rdi)
Current language:  auto; currently asm
(gdb) backtrace
#0  memcpy () at ../sysdeps/x86_64/memcpy.S:91
#1  0x00000000004004e7 in main () at test.c:8
(gdb) quit
The program is running.  Exit anyway? (y or n) y
[root~/C]

All the info handily remains in the terminal, and I have the line number that led to the seg fault.

[laserlight]

I'm using the GNU GCC compiler. Everything is as default because I'm very new to all this. Is GDB a compiler?

As MK27 has indicated, gdb is a debugger, i.e., the GNU debugger.

There are several GUI frontends to gdb, eg see here:

GUI Debugger for linux -- DDD

Of course, Code::Blocks itself is a GUI frontend for gdb, but integrated with a text editor, etc. Unless you really cannot get gdb to work with Code::Blocks, or prefer DDD, it does not make sense to use DDD in this case. Likewise...

since you are compiling and testing in the terminal too:

... you will probably not be compiling and testing in the terminal should you decide to continue using Code::Blocks. Of course, you should test in the terminal before releasing your command line program, hence you should at least know how to run your programs in the terminal anyway.