On 20/3/20 3:18 pm, Anmol Mishra wrote: > Hello, > How does the community test the rtems-tools changes? > In the README I can see a few steps, Is that the standard method?, It is my > first patch for rtems, help is really appreciated.
These files are hard to test because python is linked into gdb. To test a file you to have them installed and in an RTEMS debug session you load them and test them by using them. The actual code is brittle as it references the contents of structs internal to the kernel and these change over time. It would be really neat to have them tested and fixed if broken. To test py2 and p3 you need to build a gdb linked to each version of python and then run some tests. I know of no automated way to do this. Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
