Re: Data plugins for gdb...

["Ryan C. Gordon" <icculus@icculus.org>]

> Heh, been there, done that. :-)

I just discovered this.   :)

Maybe that's the danger of DVCS...I pulled gdb into a Mercurial 
repository, the Python stuff is in a git repo, and no hint of this was 
in the main CVS when I looked to see if anyone else had done this.

The lesson here is probably "check the mailing list archives first."

> An alternative would be to add a new element to struct type pointing to
> its pretty-printer (if any). I think this would be better, because then
> you can be very specific about exactly which type you want to associate
> with your semantically helpful visualizer. Think lookup_typename here,
> which looks up a type within a lexical block (at least that's what its
> description says).

I think that's a good idea. I was concerned about variations ("struct A" 
in C code vs "A" in C++, not to mention the usual template and namespace 
madness, non-C languages, etc).


My patch was just experimenting to see what could be done, and I was 
pretty pleased at how well I could hook in without any prior 
understanding of the gdb code. I'll take a look at the Python work.

Thanks,
--ryan.