I've gone ahead and created a "Success Stories" page within the plugin's documentation (docs/success.rst).
I took the liberty of adding links to the various bugs we've been finding in gdb - I hope that's OK - I don't want to make it appear that I'm picking on gdb (sorry!), but I did want to capture the benefit of the plugin in one place. We can reword things, of course.
You can see the HTML form of the page here: http://readthedocs.org/docs/gcc-python-plugin/en/latest/success.html
[I hope that tracking all of this manually will eventually become unmanageable, which would be, as they say, a good problem to have]
I'll expand that page to add the various bugs that the plugin shows up in itself, though I'm not sure that really counts as a "success" :)
Has anyone else found the plugin useful so far?
Dave (goes back to fixing bugs in cpychecker that compiling gdb shows up)
"David" == David Malcolm dmalcolm@redhat.com writes:
David> I've gone ahead and created a "Success Stories" page within the plugin's David> documentation (docs/success.rst).
David> I took the liberty of adding links to the various bugs we've been David> finding in gdb - I hope that's OK - I don't want to make it appear that David> I'm picking on gdb (sorry!), but I did want to capture the benefit of David> the plugin in one place. We can reword things, of course.
I think it is great.
I also wrote a cleanup checker that is specific to gdb, using your plugin. This found real bugs in gdb:
http://sourceware.org/ml/gdb-patches/2011-06/msg00408.html
Tom
On Thu, 2011-10-20 at 10:51 -0600, Tom Tromey wrote: ...
I also wrote a cleanup checker that is specific to gdb, using your plugin. This found real bugs in gdb:
http://sourceware.org/ml/gdb-patches/2011-06/msg00408.html
Thanks. I've added this to: http://readthedocs.org/docs/gcc-python-plugin/en/latest/success.html
gcc-python-plugin@lists.fedorahosted.org