Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Debugger plugin: GDB MI interface features and issues

<< < (9/10) > >>

oBFusCATed:

--- Quote from: ollydbg on October 25, 2013, 05:58:35 pm ---@obf: what about the patch in my previous post?

--- End quote ---
The plugin is in on-hold mode at the moment.
I have no intention to do any work on the plugin, until I have a proper test-suite-system for it.
I want to have some safety net, so I know that old features still work when I do changes.

If you like you can fork the repo, but don't expect to see your changes integrated in the plugin any soon.

Sorry but I can't spend any time on the plugin, because there more important things on the ToDo. :(

ollydbg:
Put some record here.
I just see there are many messages like:

--- Code: ---[debug]unparsable_output==>(gdb)

--- End code ---
When using the GDB/MI plugin, I just look at the GDB document, and I see that a full output contains this "(gdb)" token as the last token, see:GDB/MI Output Syntax - Debugging with GDB

--- Quote ---output ==>
    ( out-of-band-record )* [ result-record ] "(gdb)" nl

--- End quote ---
So, this should be fixed in the future(since you are quite busy right now,  :) )

yvesdm3000:
Has this GDB/MI project come to a halt ?

Yves

oBFusCATed:
Sort of. I plan to restart it soon.

yvesdm3000:
Biggest issue is that with an array of classes that contain a lot of other nested classes, stepping is no joy with the current implementation. Don't get me wrong, printing the object in gdb also takes minutes on this machine:

...
processor   : 23
vendor_id   : GenuineIntel
cpu family   : 6
model      : 63
model name   : Intel(R) Xeon(R) CPU E5-2643 v3 @ 3.40GHz

For now I disable the watches.

Yves

Navigation

[0] Message Index

[#] Next page

[*] Previous page