User forums > General (but related to Code::Blocks)
smallB's suggestions
ollydbg:
--- Quote from: smallB on November 08, 2011, 12:44:21 pm ---@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
--- End quote ---
@OBF:
It looks like run the command "frame 0" will give us the "next line".
BTW: I found a tiny bug in the debugger branch, when I double click on the frame 0 of the call-stack window, I looked at the debugger-log, I see that
1, "frame 0" command was send
2, "bt" command was send
So, I think "bt" command do not need to send, right?
oBFusCATed:
--- Quote from: ollydbg on November 09, 2011, 01:40:23 am ---As we have discussed, the best way was to save the breakpoint in the cbp file.
--- End quote ---
This is even worse, than saving in a separate file in the main project directory! Never do that, never ever think about it!
About the "bt" command, I'm not sure, but the reason is that the cursor has changed and the bt command is executed on cursor changed.
Not a big, deal, please don't report problems in other people topics, use the nightly build one.
killerbot:
indeed do NOT save breakpoint info in the cbp file !
This file is the project configuration, something you put in version control system. As such a file that shouldn't change because one just had a debug session, and it wants to keep some breakpoints in mind.
We have a similar mistake today, the workspace contains the active project, and therefor changes when another project is active, this is bad for version control.
smallB:
--- Quote from: oBFusCATed on November 08, 2011, 10:07:15 pm ---
--- Quote from: stahta01 on November 08, 2011, 06:13:29 pm ---I suggest you submit a patch to add a GUI to make it always do it.
--- End quote ---
No patches for this or similar features, please.
Unfortunately C::B doesn't have the infrastructure to do it right, until then (I have a plan for it),
breakpoints and watches won't be saved automatically.
It isn't that useful anyways.
--- End quote ---
I have to disagree with you on that one. How many times did you start and finish debugging a project/part of project in one session? It never happened to me so far, and I think I'm not the only one who has had this experience.
smallB:
--- Quote from: stahta01 on November 08, 2011, 06:13:29 pm ---
--- Quote from: smallB on November 08, 2011, 05:45:03 pm ---I'm not really with you. So is the answer yey or ney ;)
--- End quote ---
If your suggestions are NOT worth you doing any work; why do you think it is worth the devs doing any work.
Tim S.
--- End quote ---
It's not about that Tim. If I'd had necessary skills I'd do it myself - much easier route - no need to ask anyone, no need to convince anyone etc. you're getting the general gist. But in view of the fact that I do not posses them (yet, or maybe never) I'm merely suggesting them and is up to devs to either implement them or not. As simple as that. But believe me, when I eventually will be able to do it myself will never ask anyone, for reasons mentioned above.
Regards
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version