User forums > Using Code::Blocks
C::B debug (gdb) with breakpoints pending is VERY SLOW ...
MortenMacFly:
--- Quote from: kccheng on June 20, 2011, 06:28:09 am ---Another related question ... if I use C::B GUI to define breakpoints
by click on program's source file, how can I export the breakpoints
to external file ? Is this possible ?
--- End quote ---
Right-click in the watches windows and select the appropriate option.
ollydbg:
--- Quote ---My question is:
Is there any way to update C::B GUI so it can show all breakpoints
defined in gdb command file or initial file (gdbinit) ?
--- End quote ---
From my point of view, I think this is not implemented, which means: C::B GUI only maintain breakpoints the user sets from the GUI, if you set extra breakpoint from the debugger plugin's command line, then C::B GUI does not recognize them. Hope this can be improved.
--- Quote ---Another related question ... if I use C::B GUI to define breakpoints
by click on program's source file, how can I export the breakpoints
to external file ? Is this possible ?
--- End quote ---
I have a patch to do this, it will save all the breakpoints to an external file.
Look at:
Watches and breakpoints persistent
The only issue is: it is best to save all the breakpoints in the cbp file, not an external file, So the C::B developers were not apply this patch. :D
kccheng:
--- Quote from: ollydbg on June 20, 2011, 06:39:21 am ---From my point of view, I think this is not implemented, which means: C::B GUI only maintain breakpoints the user sets from the GUI, if you set extra breakpoint from the debugger plugin's command line, then C::B GUI does not recognize them. Hope this can be improved.
--- End quote ---
me too
--- Quote from: ollydbg on June 20, 2011, 06:39:21 am ---I have a patch to do this, it will save all the breakpoints to an external file.
Look at:
Watches and breakpoints persistent
The only issue is: it is best to save all the breakpoints in the cbp file, not an external file, So the C::B developers were not apply this patch. :D
--- End quote ---
Maybe we don't need to save all the breakpoints to an external file ?
Save them in cbp might be good enough if we have a button called "Update" or "Sync"
which will do:
1) query gdb for current breakpoints
2) check if it's in cbp file
3) if not in cbp, the C::B will remove that breakpoints and redefine it from C::B
so the GUI will be updated.
Make the "Update" or "Sync" button be used only manually, instead of try to
sync C::B GUI and gdb automatically ... this way, it will not affect performance.
(only at project open time, should has a checkbox for user to select
Update/Sync while project opened)
I think this is a good feature to add, at least, it's important to work around
slow pending breakpoints issue. Anyone with me ?
Regards,
KC
ollydbg:
Well, I'm not fully understand your idea.
Here we discuss two things:
1, you want to save breakpoints to an external file or cbp file, this way you can do breakpoints persistence, the bps will automatically loaded or added when you load a project.
2, you want to set breakpoints in a batch mode(especially you have debugee already started), this way, you stop the debugee, and run a gdb script command or other command, then gdb try to set several bps, meanwhile, the C::B GUI dialog should always updated.
Maybe, you can enhance the debugger plugin to set some "dummy breakpoints", and enabled them by context menu?
kccheng:
--- Quote from: ollydbg on June 20, 2011, 07:44:13 am ---Well, I'm not fully understand your idea.
Here we discuss two things:
1, you want to save breakpoints to an external file or cbp file, this way you can do breakpoints persistence, the bps will automatically loaded or added when you load a project.
2, you want to set breakpoints in a batch mode(especially you have debugee already started), this way, you stop the debugee, and run a gdb script command or other command, then gdb try to set several bps, meanwhile, the C::B GUI dialog should always updated.
--- End quote ---
Thanks to ask my questions by using better English :-)
Yes, both 1 and 2 are what I wanted. And I think 1) and 2) could be merged
if we provide one checkbox (or control flag) to
allow user to select whether he want to load persistence breakpoints
when project been loading.
--- Quote from: ollydbg on June 20, 2011, 07:44:13 am ---Maybe, you can enhance the debugger plugin to set some "dummy breakpoints", and enabled them by context menu?
--- End quote ---
I love to try ... but I don't know how to impl. C::B plugin yet :-( I'm new to C::B even
be a user. And I'm not good C++ programmer, but I'm quite good on C :-)
So, that will take a long time ...
Regards
KC
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version