User forums > General (but related to Code::Blocks)

Debugging on Linux?

<< < (2/2)

mandrav:
Have a read please.

agent86:
Yes, I can set breakpoints and I know about -g.  The file built with CodeBlocks debugs just fine with kdbg.  The debugging with CodeBlocks is intermittent.  The note above about "run to cursor" working...well sometimes it does, sometimes it doesnt.  Breakpoints never do.

It must be something with my build or wxGTK configuration.  The same thing has happened with ubuntu 5.10, 6.06, Debian Etch, and now FC6.  Different clean distros.  Default GCCs, libs, etc.  I installed wxGTK in its own directory in a place that I own and have built several apps using it (not with CodeBlocks).

After the new build of CodeBlocks, when I fired it up, it went looking into system space for the welcome/start-up screen, images, etc. It couldn't find anything there  in  /usr/loca/share/codeblocks directory, because all that stuff was where it should have been, in /d/linux/programs/cb/share/codeblocks where I set the prefix= to during configure after a make clean.  Why would it decide to look somewhere else all of a sudden? 

And to further annoy, now when I restart CodeBlocks, it asks again for the default compiler.  When I click on GCC, the dialog freezes and I have to kill the process.

It really should not be this difficult.  Something is just hosed.  If I must, I'll go back to eclipse.  Maybe try again in a year or so...

Thanks anyway

mandrav:

--- Quote ---After the new build of CodeBlocks, when I fired it up, it went looking into system space for the welcome/start-up screen, images, etc. It couldn't find anything there  in  /usr/loca/share/codeblocks directory, because all that stuff was where it should have been, in /d/linux/programs/cb/share/codeblocks where I set the prefix= to during configure after a make clean.  Why would it decide to look somewhere else all of a sudden?
--- End quote ---

It's a bug which appeared the last couple of days. I will commit the fix for it in a while.


--- Quote ---It really should not be this difficult.  Something is just hosed.
--- End quote ---

It usually isn't difficult.


--- Quote ---If I must, I'll go back to eclipse.
--- End quote ---

If you must, then please do so.

agent86:
I found the problem.  I wrote a nice long description but when I pressed on Post it all disappeared.  So the short form is:

If a breakpoint is placed at the first executable statement of  main(), then it is not properly placed into the executable (my assumption) and it is thus ignored.  (That is where I put the breakpoints to see if degugging worked.  It didn't...there).

I'm happy now.

mandrav:

--- Quote ---I'm happy now.
--- End quote ---

I 'm glad you sorted it out :).

Navigation

[0] Message Index

[*] Previous page