[PATCH 1/2] covoar: Add symbol set reader and ELF data parser to covoar.

[Cillian O'Donnell]

On Fri, 27 Apr 2018, 04:48 Chris Johns, <chrisj at rtems.org> wrote:

> On 27/04/2018 08:51, Joel Sherrill wrote:
> >
> >        // Create the set of desired symbols.
> >        SymbolsToAnalyze = new Coverage::DesiredSymbols();
> >     -  SymbolsToAnalyze->load( symbolsFile );
> >
> >
> > I am having trouble seeing what happened to the DesiredSymbols class. Is
> > it no longer needed?


It's still being used as before, the decision has just been split from did
you provided the symbols file or are you using symbol_set.cfg file.
DesiredSymbols is definitely still being used. I'm looking on my phone  so
maybe missing something that would be clearer not on a phone.

Just to update, I didn't get time to look at the rsb build yesterday so
it'll have to be tonight. Sorry for the delay, my new job keeps me very
busy during the week, long commutes too.

Did

we change the class from which SymbolsToAnalyze
> > is derived but provide all the same needed interfaces?
> >
> > I'm having trouble seeing how the new class fits in. Help me.
>
> I am adding support to determine the build top from the executable path(s)
> and
> to verify the build path, arch prefix and BSP match for all executables
> passed
> in and then I will load the symbols from the libraries listed in the
> config file
> directly into the desired symbols class. It looks me like these extra
> classes
> are not needed.
>
> Chris
>
> _______________________________________________
> 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/20180427/8b00553f/attachment-0002.html>