User forums > Using Code::Blocks
Debugging session gets frozen
dr snuggles:
I'm having the same issues as VincentB. I was using the g++ and gdb from my dev-cpp directory so I thought these could cause problems. After downloading and installing MinGW 5.1.3 and GDB 6.3, I changed the compiler and debugger path in C::B.
Compiling goes well, but debugging gives some weird errors:
--- Code: ---Starting debugger: done
Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints
Debugger name and version: GNU gdb 6.3
Child process PID: 2932 <--- Never got this message with the old debugger
At *removed_filename*.cpp:49 <--- Normal message, but debugger hangs from here, as it always did
Trying to pause the running process... <--- Can't abord, have to shut down C::B
Trying to pause the running process...
--- End code ---
So this is even worse then the old behaviour: I can't stop de debugger anymore :o. Replacing gdb.exe (6.3) with gdb.exe (5.2.1) gives me the random hanging behaviour I'm used to, so I'll use that for the moment.
Edit: Changing the default compiler doesn't work either. Plus: the auto detect function forgets to update the search directories, resulting in some weird errors if you don't change it manually. Is there a way I can report all my bugs in an easy way without having to register at a website again?
tmt:
I have this bug too. I've found two possible workarounds:
1. Disable 'evaluate expression under cursor' feature - this often caused the discussed error, though not always the reason.
2. When debugger gets frozen, open task manager and kill gdb manually. C::B continues normally.
:shock:
VincentB:
Dear all,
I have installed nightly build 3683 (11th March) and the situation got worse, as with some big project I am currently working on, the breakpoints set through C::B do not cause any break. This is happening with nightly build 3683 both with gdb 5.2.1 and with gdb 6.3 which I have just installed according to isntructions from Mr Biplab.
With the "Hello world!" program that contains a loop which I sent in a previous e-mail + the GDB 6.3, the breakpoint on row 7 ({for(int i = 0; i < 10; ++i)) causes a break as wanted both with nighly build 3677 and 3683, and the 3683 still has the same freezing problem as 3677 on row 13.
Furthermore, the 3683 has an additional problem compared to 3677, as when the freezing problem occurs it is not possible to stop the debugger (GDB 6.3) by the menu "Stop Debugger", and the only solution is to kill everything. I tested nightly build 3683 only with gdb 6.3 and no gdb 5.2.1.
With 3677 it was possible, on occurrence of the freezing problem on row 13 to stop the debugger by the "Stop Debugger" menu, both with gdb 5.2.1 and gdb 6.3.
Here is the output of nighly build 3677 with gdb 6.3 when I make the freezing problem test and I exit by "Stop Debugger":
Building to ensure sources are up-to-date
Build succeeded
Selecting target: Debug
Adding source dir: D:\users\vbl\local_dev\test_CB\Test_CB\
Adding source dir: D:\users\vbl\local_dev\test_CB\Test_CB\
Adding file: .\test_CB.exe
Starting debugger: done
Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints
Debugger name and version: GNU gdb 6.3
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:7
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:9
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:7
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:9
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:7
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:9
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:7
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:9
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:7
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:9
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:7
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:9
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:7
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:9
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:7
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:9
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:7
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:9
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:7
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:9
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:7
At D:/users/vbl/local_dev/test_CB/Test_CB/main.cpp:13
Debugger finished with status 1
The line Debugger finished with status 1 is caused by my invoking "Stop Debugger" because I am frozen on row 13 (std::cout << "Hello world!" << std::endl;). The "i" variable appears in the Watches window in red as i = no symbol "i" in current context
With nighly build 3683 + gdb 6.3 when I make the freezing problem test, I get almost the same output, except that when I am stuck on line 13, and I try to exit by "Stop Debugger" , the line "Debugger finished with status 1" in the debugger output pannel, is replaced by "Trying to pause the running process...", and the debugger is not stopped, and I have to kill it by the task manager.
Hoping that these information can help to solve this issue,
Vincent.
Navigation
[0] Message Index
[*] Previous page
Go to full version