This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Add fullname to breakpoint output

To my mind, as long as you have "ui_out_text" sprinkled amongst the result accumulating statements in "core" gdb, you have CLI code embedded in the core gdb functionality. After all, the "text" output was just a clever way to continue formatting stuff up for the CLI without polluting the MI output. But having it there means command output can't be changed without potentially messing up the CLI output - the two are still intimately linked.

disasm.c has a bunch of ui_out_text calls.


On Sunday, April 13, 2003, at 09:14 PM, Andrew Cagney wrote:

Yes, this is a desirable goal. Have you thought about how to do this?

The best way I can think of is to have a new ui_out that builds up an intermediate representation for results that is easy to access randomly - making up real lists & dictionaries from the ui_out_field_xxx and list & table stuff. Then we could banish ui_out_text & friends to the CLI commands to take the whole result, pull bits out in the order they expected, and annotate them with text, newlines, etc, in order to make a nice display.
In practice, this will be gnarly to get right, but you could do it incrementally by getting the intermediate rep. ui_out working, then fix the CLI commands one by one by swapping in the new ui_out for those commands you had fixed, and using the old CLI one for the commands you hadn't gotten working...

I don't know that anything that complicated is needed. disasm.c worked out pretty well.


Jim Ingham                                   jingham at apple dot com
Developer Tools
Apple Computer

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]