User forums > Help
Debugger sometimes stalls when using "Step Into".
cbuser2:
--- Quote from: and4cb on November 20, 2012, 07:30:48 am ---
I am trying to use C::B to update a C program, and I need to "Step Into" each function. Please let me know why sometimes, when I "Step Into" a function, all of the debug options are disabled (greyed out).
When this happens, the "Stop Debugger" button also does not work, and the Command box in the Debugger window will no longer accept commands?
When I click on the "Stop Debugging" box, the only message I receive is: "Trying to pause the running process..."
--- End quote ---
I am using 21.11 Nightly on Win 7 64-bit.
This also randomly happens to me too. Can't close the output console, can't stop the debugger, debug options greyed out. Only closing CB will fix the problem.
MortenMacFly:
--- Quote from: jens on November 20, 2012, 09:38:24 am ---Here is the xp log.
[...]
--- End quote ---
Out posts crossed.
Although I cannot reproduce too on Won7/64 bit, the only difference between the log is:
[debug]> catch throw
[debug]Function "__cxa_throw" not defined.
[debug]Catchpoint 1 (throw)
...for Jens, which means that he has enabled "catch c++ exceptions" in the debugger settings which should not be the cause (however, @and4cb: you may wanna try).
Then, for and4cb it stops where Jens shows this output:
[debug]C:\new\testc\main.c:31:632:beg:0x401391
@and4cb: May sound a bit weird, but can you do the log again and write into the log a note when exactly you saw what in the log and hit what button?
oBFusCATed:
--- Quote from: MortenMacFly on November 20, 2012, 01:22:30 pm ---@obfus: After such a long time bugging you - I had to do it... ;-)
--- End quote ---
As far as I can see, this is unrelated.
If you can reproduce it and then verify that you've fixed it correctly, I've no problem with it.
I've not been able to reproduce it reliably in order to fix it and as you know the state-machine is a bit fragile.
oBFusCATed:
BTW: The problem happens (probably), because there is missing line:
--- Code: ---[debug]C:\Code\test5\main.c:31:632:beg:0x401391
--- End code ---
After the line:
--- Code: ---[debug]InitNum (num=4) at C:\Code\test5\main.c:31
--- End code ---
But I don't know why this line is missing :(
MortenMacFly:
--- Quote from: oBFusCATed on November 20, 2012, 01:48:45 pm ---As far as I can see, this is unrelated.
--- End quote ---
Maybe... but who knows.
--- Quote from: oBFusCATed on November 20, 2012, 01:48:45 pm ---If you can reproduce it and then verify that you've fixed it correctly, I've no problem with it.
--- End quote ---
I've fixed the "out of bounds" problem most likely correctly - see here:
http://svn.berlios.de/wsvn/codeblocks?op=comp&compare[]=/@8581&compare[]=/@8582
The problem was, that after this message came up, the debugger's internal state was still set to "m_ProgramIsStopped = false" which is wrong in that case. You can confirm that easily by having a "hello world" console app, set a BP in the "return" statement and just continue stepping through the "OS DLL" code until you get that message. It froze the debugger before, now it doesn't.
The same flag would be a candidate for the problem described here (surely another code segment though).
My guess is, that if the BP message does not show up (why-ever) this state is not covered properly, so any following actions like "pause debugger" will lead to nowhere. Maybe after the first "pause" which failed we should try to fiddle with this internal state, too... not a hack, but properly done.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version