User forums > General (but related to Code::Blocks)
smallB's suggestions
oBFusCATed:
Haha, I've the same problem myself yesterday, I had -O2 and -s and I wanted to debug, stupid me, lost a bit of precious time.
About feature no 5, I doubt, gdb supports this, smallB if you can tell me the command I can probably do something about it.
But I've never used this feature in VStudio...
smallB:
--- Quote from: ollydbg on November 08, 2011, 10:04:39 am --- Next time you meet such a problem, I suggest you need to post the "full build log" and the "full debugger log".
--- End quote ---
Absolutely agree. Will remember next time. Thanks.
smallB:
--- Quote from: oBFusCATed on November 08, 2011, 10:19:14 am ---Haha, I've the same problem myself yesterday, I had -O2 and -s and I wanted to debug, stupid me, lost a bit of precious time.
About feature no 5, I doubt, gdb supports this, smallB if you can tell me the command I can probably do something about it.
But I've never used this feature in VStudio...
--- End quote ---
I'm not sure about the exact command but it will have something to do with next statement to be executed.
The whole point of having that, is that when you are in debugging process sometimes you want to check something without canceling the whole debug process. So you go let's say to another file and you're checking some definitions, then you go to another/or the same file and checking another things. After you done you would like to continue debugging but you don't remember where was it (which file, which line) the only options at the moment is either find manually the point where you stopped before you decided to check something or press one of: "next line", "go into" or "step out". This isn't always satisfactory because one of those steps may go into fnc which will cause exception and you won't know which line it was so you cannot prepare yourself for that next time. Instead you have to repeat whole debugging process all over, cause exception, remember the exact place and start debugging again.
With what I propose you would just press "show next statement" and you'd be brought back to where you left off.
Thanks.
ollydbg:
--- Quote from: smallB on November 08, 2011, 12:07:28 pm ---After you done you would like to continue debugging but you don't remember where was it (which file, which line) the only options at the moment is either find manually the point where you stopped before you decided to check something or press one of: "next line", "go into" or "step out". This isn't always satisfactory because one of those steps may go into fnc which will cause exception and you won't know which line it was so you cannot prepare yourself for that next time. Instead you have to repeat whole debugging process all over, cause exception, remember the exact place and start debugging again.
With what I propose you would just press "show next statement" and you'd be brought back to where you left off.
Thanks.
--- End quote ---
Ok, for this feature request, I always double click on the lowest frame in the "call stack" window, then I return to the "next statement" position. :D
smallB:
@ollydbg, yes, sure that is good workaround but I think (if it's not to hard to implement) it would be nice to have it on a debugging toolbar.
Just a thought.
Regards
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version