User forums > Help

debugging on linux: strange symbols, files open twice, "nothing to be done"

(1/5) > >>

CuteAlien:
I noticed a few troubles when debugging on linux:

1. When I hit successive shortcut keys for debugging fast, then that does not execute the action but instead it inserts strange symbols into my code. Like Ś for F7. So I must always be careful to step only very slow.

2. The debugger always opens files which are already open once more. So if I have for example src/main.cpp open, set a breakpoint and start debugging then the debugger will open main.cpp (without src/ in the name) and stop there at the breakpoint (the breakpoint symbol will not be shown in this view - only in the other one).

3. When I stop a build and then go on "start debugging" I only get told "nothing to be done" and the debugger does neither start nor try to build. I have to change a sourcefile to get it working again.

I would be glad on any hints how to avoid those problems.

I'm using 8.02 with Build: Mar 17 2008, 00:38:40 - wx2.8.7 (Linux, unicode)

Jenna:
Is your project in a directory that is a symbolic link to another ?

If yes read this post and my solution for it.

That can cause the double open files and maybe also that C::B does not recognize the changing of the file-stamp.

I'm not sure if the other problem is fixed in trunk (it happened to me from time to time, but test today worked without error, even if I kept the F7 key pressed).
You may want to try a more recent nightly.

CuteAlien:
Yes I am using relative links, I should have mentioned that. Using mount instead of ln is certainly an interesting solution, I'd never had thought of that :-) But opening the project with the absolute path also does seem to work.

I might try a newer nightly, but can't do that right now. Guess I will just have to be careful for a while when debugging.

Thanks for your help.

edit: I switched to mounting by now, as I still had sometimes problems with the path. That has solved it now.

CuteAlien:
I just tried a current nightly build (from your app sources) and the problem with F7 is indeed fixed :-)

Still some debugging troubles left unfortunately, like sometimes the application suddenly continues running while I'm still in the debugger (it's not multithreaded). And I'm rather certain I don't accidently press strg+F7. Also I haven't yet found out how to display wchar_t's.

But having those strange characters gone is already a big improvement!

CuteAlien:
Another debugging problem :-(

The debugger can often not find local variables. I just get "No locals" in the Watches view or "no symbol X in current context" when trying to use mouse-over. Function Arguments including this object are available.  Any ideas?

Navigation

[0] Message Index

[#] Next page