Hi I am thrilled to see this code finally becoming more widely available. I am now asking questions about "productization" which is reproducibility, maintainability, making it available to users, enhancement path, etc.
Would it be possible to update the blog to reflect the current location of the code? Chris.. does having this in rtems-tools mean that a standard *-rtems* gdb will have the Python pretty printers? Is there an up to date status of which core handlers and managers have at least an initial pretty printer? Is there anyway to automate testing these? I know the gdb macros that I mostly wrote were a pain in the *&%$ to make sure they stayed up to date and in sync. It was easy to miss them for months after a change impacted them. --joel On 8/24/2014 6:45 PM, Chris Johns wrote: > Module: rtems-tools > Branch: master > Commit: 6e75f4ebf5450154231a1f7c1c2ba97e60d2c074 > Changeset: > http://git.rtems.org/rtems-tools/commit/?id=6e75f4ebf5450154231a1f7c1c2ba97e60d2c074 > > Author: Dhananjay Balan <mb.dhanan...@gmail.com> > Date: Tue Jul 9 22:39:27 2013 +0530 > > Update readme. > Included useage instructions. > > --- > > tools/gdb/python/README.md | 2 ++ > 1 files changed, 2 insertions(+), 0 deletions(-) > > diff --git a/tools/gdb/python/README.md b/tools/gdb/python/README.md > index 567c195..8858a4f 100644 > --- a/tools/gdb/python/README.md > +++ b/tools/gdb/python/README.md > @@ -2,3 +2,5 @@ rtems-gdb > ========= > > GDB extenstions to RTEMS. > + > +See [this blog post for > instructions](http://dbalan.github.io/blog/2013/06/23/debugging-rtems-with-gdb/) > > _______________________________________________ > vc mailing list > v...@rtems.org > http://lists.rtems.org/mailman/listinfo/vc -- Joel Sherrill, Ph.D. Director of Research & Development joel.sherr...@oarcorp.com On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (256) 722-9985 _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel