stavefan
07-31-2001, 08:22 AM
Hi all,
I was wondering if anyone else had this problem and knew a work-around....I am using k studio gold(which is built on top of kdevelop) and am pleased with the interface. The problem that I am having is that the debugging information compiled into the executable (i have debugging turned on) is not all that great. It seems that once multiple threads are established, the debugger (which is kdbg) cannot/will not break properly or step through code.
My question boils down to this...what gcc compiler option can i use to get the most debugging information into the executable? I know that there is a -g option for debugging, but i've also seen -g1, -g2, -g3...what is the difference, is this even what i want?
Thanks for any help,
stavefan
I was wondering if anyone else had this problem and knew a work-around....I am using k studio gold(which is built on top of kdevelop) and am pleased with the interface. The problem that I am having is that the debugging information compiled into the executable (i have debugging turned on) is not all that great. It seems that once multiple threads are established, the debugger (which is kdbg) cannot/will not break properly or step through code.
My question boils down to this...what gcc compiler option can i use to get the most debugging information into the executable? I know that there is a -g option for debugging, but i've also seen -g1, -g2, -g3...what is the difference, is this even what i want?
Thanks for any help,
stavefan