So, I'm going to program some C

*grabs debugger*

*grabs -O3*

I keep seeing it here, but what actually is -o3 ?

>>3
The compiler equivalent of V-TEC, it really speeds up a compiled program.

_{hax my anus}

>>1
You don't need a debugger to program in C.

>>6
I don't need a debugger to program in C?  How do I inspect the state of my program at runtime?

It's dangerous to go alone take this!

*grabs dick*

xD

>>7
IMHO a debugger is a tool of last resort. Once you have exhausted every other avenue of diagnosis, and have given very careful thought to just rewriting the offending code, *then* you may need a debugger.

>>7
Terrible!

every other avenue of diagnosis
void main() {
    int i, j, *k;
    printf( "ENTERING MAIN LOOP\n" );
    printf( "SETTING VARIABLES\n" );
    i = 1;
    printf( "i=%d\n", i );
    j = 2;
    printf( "j=%d\n", j );
    k = 0;
    printf( "k=%d\n", k );

    printf( "PERFORMING LOGIC\n" );
    if ( i == j ) {
        printf( "THE VALUE OF I IS EQUAL TO J\n" );
        printf( "SETTING I TO THE VALUE AT K\n" );
        i = *k;
    }
    else {
        printf( "I = %d AND J = %d\n", i, j );
    }

    printf( "TIDYING UP THE STACK\n" );
}
Because using gdb to find the bug is much too difficult, and involves setting EXPERT CFLAGS.

>>11
This is not valid Java code. WTF are you doing?

>>9
How about you save us all a lot of headache and catch your memory errors with your debugger before making a release?

jdb is the Java debugger, incase you didn't know.

Debuggers are only useful to people that write buggy code.

>>15
I.e. you.

>>11,13
Since I started using Test Driven Development in 1999, I have not found a serious use for a debugger. The kinds of bugs I have to troubleshoot are easily isolated by my unit tests, and can be quickly found through inspection and a few judiciously placed print statements.

DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS DEBUGGERS

I have never used a debugger in my two years of Haskelling :(

>>19
Now you have 2 problems.

Ah hate dem buggers

>>20
No, I never had a problem.

anus anus anus :(

I have never used a debugger in my two years of Haskelling :(

>>22

>>24
How does this post make sense?

>>25
I think >>24 was highlighting >>19,22's two problems.

I never need to debugger my code because i never bugger it to begin with.

>>9,17
2/10

I would gladly use GDB if it wasn't so unfriendly. But since it is, it's back to manual traces...

>>28
0/0

>>29
The only thing I really use GDB for is backtracing a segfault/etc. so I can find out where to look, and see the values of the variables at the time of the crash. Then it's back to manual traces.

>>29
Try M-x gdb or DDD.

>>31
Is there any other use?

>>31
valgrind + gdb =EXPERT DEBUGGER

DDD was very useful. Sadly, it died on 2008-05-06.

(2008/05/06) New plans for DDD. The ne problemw maintainer has communicated to the official DDD distribution list about the intention of change the GUI to a Qt based interface. At the end, it seems that what is going to happens is that DDD will have two branches, one with a GUI based in Qt and other based in Gtkmm, with a common core that will be independent of the GUI. So, it will be possible putting any other GUI based in any other library. As you know Qt is GPL v3 licensed.

Erika once told me that Xarn is a bad boyfriend