Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Splitting debugger in two - specific debugger and common GUI
oBFusCATed:
But then you'll have to do the job twice, I guess.
Jenna:
--- Quote from: oBFusCATed on January 05, 2012, 10:25:08 pm ---But then you'll have to do the job twice, I guess.
--- End quote ---
I do it in the wxsmith-branch, and if it is ready, it can be merged back into trunk.
MortenMacFly:
--- Quote from: jens on January 05, 2012, 10:07:52 pm ---Can we wait with a merge, until the linux and windows build fixes (and directory layout changes) are made ?
--- End quote ---
Yes, sure - I won't do it overnight. ;-) Although I wonder what is still pending. It looks pretty good now.
I have (however) prepared to merge the wxPropGrid changes from the debugger branch into trunk. This will than also land (sooner or later) in the wxsmith branch.
MortenMacFly:
I had the following issue several times now:
While debugging, I pressed "Next" several times to debug step-by-step and suddenly all debugger buttons are greyed out, except the "Pause " and "Stop". But hitting these does nothing. I have to kill the debugger (notice that killing the debugger's debuggee does nothing, too) to get C::B back to work.
In the debuggers debug log I see:
--- Code: ---[debug]> next
[debug]Cannot find bounds of current function
[debug]>>>>>>cb_gdb:
Trying to pause the running process...
--- End code ---
And that's basically it. Even if hitting the "Stop" button several times.
What's causing this? Anybody here experiencing the same?
oBFusCATed:
Do you have the full log?
Do you have a 100% reproduction case?
My guess is broken GDB/Debug info and also it is caused by not well parsed output from "next".
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version