|Re: [cdt-dev] Pretty printer bug number|
That is a good idea. It is a small enough patch. Could you make the request on the bug so it does not slip between the cracks?
> Marc, this is nice! I'm seeing the pretty printed display of strings, maps, vectors, etc. This is going to make a lot of people happy.
> Are the plans to commit this to only the 3.6 branch, or is there any chance it will be in 3.5.2 as well?
Actually, MI does support pretty-printing but it requires some special request from DSF-GDB to turn this on.
> Have you given thought to what it would take to be able to toggle the actual variables between a pretty-printed view and a raw view?
> It means completely avoiding use of the -var-list-children MI command, since that still reports the raw format.
> Would it be easy to inject an alternate handling of variables that issued the cli print command and interpreted its results?
I don't think it would be very hard, but I've been so busy with so many other things that I didn't have time to figure
out what those MI changes are. They are all documented in GDB... Someone just needs to take the time to read it and digest it.
If someone from the community could try making some headway on it, that would speeds things up.
I'm not familiar with that extension point, but in DSF and DSF-GDB, we don't use any extension points.
> Or does DSF support anything like the org.eclipse.debug.core.logicalStructureProviders extension point?
It's nice to see interest on this fix.
On Tue, Jan 5, 2010 at 8:27 AM, Marc Khouzam <marc.khouzam@xxxxxxxxxxxx<mailto:marc.khouzam@xxxxxxxxxxxx>> wrote:
as discussed in the conference call, here is the bug that focuses on support for GDB 7.0 pretty printers for DSF-GDB
There is a prototype patch attach that is small and easy to try.
cdt-dev mailing list
Back to the top