[GSoC|RTEMS-GDB] Project status.

[Dhananjay Balan]

RTEMS GDB Updates

A) The framework has undergone major re factoring. The code has been
separated into following modules and this design will be followed in future,

This is done mainly to reduce the clutter and to increase the re-usability
of the code.

 1) Object abstractions will go into a module of their own name or into a
module corresponding to the parent API. (e.g CORE_ data structures are in
the supercore module)
 2) Pretty printers will go into $api_name_printers
 (e.g id_printer is in supercore_printer)
 3) Helper routines will be grouped into their own modules (ToDo as of
current master)

B) rtems object command now prints message_queue objects and I want to get
an opinion on its implementation.

If you look at the code,
classic.message_queue creates a supercore.CORE_message_queue object, and
each have a method to print the contents.

What I am intending to do is to add all the classic api objects into this,
and then refactor again
 - Move all the helper routine methods out of the main abstraction
 - to have a robust inheritance in the code.

C) Testing the code.
A testing framework can ensure that the code in this repository stays
current as rtems moves forward. The idea is to write tests against a
pre-defined sample code.

Please go through the code at github and shoot any commends criticisms you
have.

Note: the repo is here https://github.com/dbalan/rtems-gdb


On 23 June 2013 21:28, Dhananjay Balan <mb.dhananjay at gmail.com> wrote:

> *
>
> Hi,
>
> I was little bit delayed by my academic responsibilities, but I have moved
> out and everything is in order so that concentrate
>
> exclusively on the SoC. I have created a github repository[1] to push my
> work. I am starting from what chris wrote and refactoring on the go.
>
> What I am done so far:
>
> * Read and understood the GDB python API
>
> * Initial scan through the RTEMS docs.
>
> * GDB developer agreement completed
>
> * A blog post on how to use the debug extenstions (Nothing new, but I plan
> to blog along with my work progresses, and this will be the first in it)[2]
>
>
> What I will be doing next week:
>
> * Pretty printers - Lots of pretty printers
>
> I intend to start with the classic api, some parent objects in the
> hierarchy is already implemented by Chris, My approach is to start from top
> and implement them on the go.
>
> * Port simple commands from rtems-gdb script, that utilizes the pretty
> printers - it will also help for others to test my code.
>
> I will update the work progress here by mail, and also in my blog.
>
>  [1] https://github.com/dbalan/rtems-gdb
>
> [2] http://dbalan.github.io/blog/2013/06/23/debugging-rtems-with-gdb/
>
>
> *
>
> --
> Dhananjay




-- 
Regards,
Dhananjay M Balan,
Department Of Computer Science,
College Of Engineering, Trivandrum.
http://cet.ac.in
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20130712/0271807b/attachment.html>