[PATCH 11/25] Merge sapi/Makefile.am into cpukit/Makefile.am

[Vijay Kumar Banerjee]

On Mon, 1 Oct 2018 at 11:22, Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> On 25/09/2018 07:58, Chris Johns wrote:
> > On 25/09/2018 15:30, Sebastian Huber wrote:
> >> On 25/09/2018 00:27, Chris Johns wrote:
> >>>>>> We would have to go from the symbol to the ELF file to the DWARF
> info of the
> >>>>>> compilation unit.
> >>>>> All info should be directly via the ELF and DWARF format. I do not
> know if we
> >>>>> need to reference the ELF symbol table or we can just use the DWARF
> CU data.
> >>>>> The
> >>>>> use of objdump should be avoided.
> >>>> I only briefly look into this, but you have to go from the
> rld::symbols::symbol
> >>>> to the DWARF info somehow if DesiredSymbols.cc:95 is the right spot
> to add this
> >>>> stuff.
> >>>>
> >>> You could be right. The DWARF info will contain all symbols and more.
> >>>
> >>> Should these files move to the rtems.git repo?
> >> The *.ini files or which files?
> > Just the INI files, the files which describe the data.
> >
> >> I would leave the files where they are and fix
> >> the issues first. Afterwards I would think about moving files around
> across
> >> repositories.
> > Oh of course, that is fine and it makes sense. I would like to
> understand the
> > tasks and agree on them.
>
> This stalled my background work on general RTEMS improvements (in this
> case the build system). I think the path is clear. We use source tree
> path regular expressions to assign source files to categories. The
> source tree path is determined for each symbol by the DWARF compilation
> unit information. The categories are defined in an INI file in
> rtems-tools for now. Maybe later it is places somewhere else.
>
> I would like to continue now with the build system changes. This will
> break the coverage tool categories for some time.
>
> Is there some documentation on how I can use the coverage tool? Which
> BSP is recommended for test runs?
>
> There isn't proper documentation of this, but the following wiki page
has the instruction of how to run the coverage tool.
https://devel.rtems.org/wiki/GSoC/2018/coverage_analysis_toolset

The coverage tool worked properly with leon3.

-- 
> Sebastian Huber, embedded brains GmbH
>
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> Phone   : +49 89 189 47 41-16
> Fax     : +49 89 189 47 41-09
> E-Mail  : sebastian.huber at embedded-brains.de
> PGP     : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20181001/d6ceddde/attachment-0002.html>