Covoar address to line to DWARF updates.

Vijay Kumar Banerjee vijaykumar9597 at gmail.com
Fri May 25 03:56:22 UTC 2018


On Fri, 25 May 2018, 02:52 Chris Johns, <chris at contemporary.net.au> wrote:

> On 25/5/18 7:11 am, Vijay Kumar Banerjee wrote:
> > On Fri, 25 May 2018, 00:35 Joel Sherrill, <joel at rtems.org
> > <mailto:joel at rtems.org>> wrote:
> >     On Thu, May 24, 2018, 10:43 AM Vijay Kumar Banerjee
> >     <vijaykumar9597 at gmail.com <mailto:vijaykumar9597 at gmail.com>> wrote:
> >         On 24 May 2018 at 18:58, Vijay Kumar Banerjee <
> vijaykumar9597 at gmail.com
> >         <mailto:vijaykumar9597 at gmail.com>> wrote:
> >             On 24 May 2018 at 18:21, Gedare Bloom <gedare at rtems.org
> >             <mailto:gedare at rtems.org>> wrote:
> >
> >                 Vijay,
> >
> >                 Please test Chris' modifications.
> >
> >                 On Thu, May 24, 2018 at 2:23 AM, Chris Johns <
> chrisj at rtems.org
> >                 <mailto:chrisj at rtems.org>> wrote:
> >                 > Hi,
> >                 >
> >                 > I have pushed my latest set of changes to my personal
> repo to remove covoar
> >                 > exec'ing addr2line and to directly use the DWARF debug
> info.
> >                 >
> >                 > I have not been able to fully test the results because
> I do not have a suitable
> >                 > .exe and .cov pair with match source. The executable
> and coverage data I have
> >                 > received has helped but objdump fails because I do not
> have the source in the
> >                 > executable path so does not find the source.
> >                 >
> >                 > I would like to get these changes on to master as soon
> as possible so if a
> >                 > covoar built from my repo can be tested I can then
> push the changes to master.
> >                 >
> >                 > I have added to RTEMS Tools an addr2line utility as I
> needed a tool to test the
> >                 > DWARF support I have added to the rtemstoolkit.
> >                 >
> >                 > The repo is
> https://git.rtems.org/chrisj/rtems-tools.git and the changes are on
> >                 > the branch 'covoar-dwarf'.
> >                 >
> >
> >              Hello ,
> >             I have added the .cov trace file and the objdump output of
> hello.exe
> >             that I'm getting.
> >             Is there anything else I should be doing to test it ?
> >             Shall I send the txt reports generated from covoar ?
> >
> >
> >         I merged your branch with my current working branch that's
> >         producing html reports.
> >         When I run in for samples/ I'm getting some report that looks
> good.
> >         But when I run for the whole testsuites. It trips in the middle
> after a
> >         lot of
> >         INFO messages. It shows the following error:
> >
> >         ===========
> >         .
> >         .
> >         .
> >         INFO: DesiredSymbols::createCoverageMap - Attempt to create
> unified
> >         coverage maps for CSWTCH.1 with different sizes
> >
>  (/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/libtests/mghttpd01/mghttpd01.exe/2148!=
> >
>  /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/benchmarks/dhrystone/dhrystone.exe/16)
> >         error: SymbolTable::addSymbol: Different lengths for the symbol
> CSWTCH.1
> >         (16 and 544)
> >         error: covoar failure exit code:
>
> Is this the error that stops covoar?
>
> yes
> >
> >     This is the symbol loading picking up rodata merged into the text
> segment.
> >     Chris know about this and it is on his to-do list.
> >
> >     Can you ignore these and see how the results look?
> >
> > it doesn't show results, it exits in the middle with the error, even
> before
> > coverage starts generating reports.
> >
>
> Is that the error message above?
>
> yes
>

Chris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180525/e819a810/attachment-0002.html>


More information about the devel mailing list