This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] varobj.c: Report changed values that use a pretty-printer
> Nick> There have been a few problems, notably changed values don't seem
> Nick> to get reported by -var-update. The patch below seems to fix
> Nick> this.
>
> Oops, bad timing ... I have a big patch to redo all this code, as
> discussed on the gdb list and the archer list. It is on the
> archer-tromey-python branch, but I plan to push it to CVS as soon as
> Volodya declares it ready (and as soon as I tidy up the documentation,
> my task for tomorrow).
No problem, it was only a small patch. Were you aware that changed values
aren't reported? Does your patch fix the problems that I mentioned?
> Nick> The scope of this work seems enormous as it opens the possiblity
> Nick> of formatting the watch expressions of all STL containers (as,
> Nick> ISTR, is already done in Totalview). Of course the amount of work
> Nick> it entails is probably enormous too and the problem, as always, is
> Nick> finding someone to do it.
>
> GCC svn trunk has pretty-printers for basically everything in libstdc++ :-)
Cool! Will they be distributed as part of the libstdc++ package files?
i.e. with future GNU/Linux distributions
> I'd like to write printers for some other programs (gdb, or gcc, or
> python, or emacs) but haven't found the time ...
I'm not sure what you mean. I was thinking of writing lisp code so that
Emacs can parse the output of the pretty printers like the ones you describe
above.
--
Nick http://www.inet.net.nz/~nickrob