Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
oBFusCATed - gdbmi plugin query
AndrewCot:
To implement the memory range code I need to take time to get more of an understanding of the exisitng code and as such I have started working on the edit breakpoints.
When I started to look at the edit breakpoint functionality I found that there is a bunch of work as the existing dialogs are missing and the existing GDBMI breakpoints are only code only.....with no support for data or function types. With these changes I would not do any testing with the existing as the main breakpoint and code have to change.
Does the existing GDB debugger support function breakpoints? I can see some support, but not enough in my 2 minute check.
AndrewCot:
I have wired up missing dialogs below so they display like the existing GDB debugger, but they do nothing as there no functionality to use them yet:
* debugger_options_dlg.xrc
* debugger_project_options_dlg.xrc
* edit_watches_dlg.xrc
BlueHazzard:
I have used data breakpoints in the past.
Never tried function break points, and i think there is no UI to add them, or am i wrong?
AndrewCot:
That's what I seen with the code for the function breakpoints and was why I was asking as it seemed like it was partially coded and not completed in the existing GDB debugger. It will end up being the same for the GDB/MI first version as I am porting the same code over with mods to get it working with the new way of doing things in the GDB/MI code.
AndrewCot:
I know this is a loaded question (I am 99.99% sure the answer is no), but:
Is there a list of GDB features that are missing from the existing GDB debugger? This assumes right or wrong that that GDB is at least 9.1.0. The reason 9.1.0 as it was when version 3 of the GDB/MI version 3 was introduced
GDB/MI version "breaking" changes:
# GDB Change
1 5.1 None
2 6.0 The -environment-pwd, -environment-directory and -environment-path
commands now returns values using the MI output syntax, rather
than CLI output syntax.
-var-list-children's children result field is now a list, rather
than a tuple.
-var-update's changelist result field is now a list, rather than
a tuple.
3 9.1 The output of information about multi-location breakpoints has
changed in the responses to the -break-insert and -break-info
commands, as well as in the =breakpoint-created and
=breakpoint-modified events. The multiple locations are now
placed in a locations field, whose value is a list.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version