[PATCH v3] covoar: Handle periods in symbols from objdump

[Joel Sherrill]

On Tue, Mar 16, 2021, 4:47 PM Alex White <alex.white at oarcorp.com> wrote:

> > Do any non-compiler-generated symbols include "."?
>
> Yes, according to the output of nm:
>
> $ i386-rtems6-nm build/i386/pc686/testsuites/libtests/block08.exe | grep "
> \."
> 0011bdd2 t .check_stack_switch
>
> I don't think there are any function symbols that include ".", though.
>

I don't think including a dot is legal in any programming language we are
interested in. Holy qualified names in Ada use dot in fully qualified names
between the parts but that is mangled in the compiler.

>
> >
> > Are there symbols that start with a "." that might be caught? I know we
> do
> > this in assembly programming often, e.g., ".vectors", although probably
> it is
> > unlikely to appear in C/asm I just want to be thorough.
> >
>
> I didn't spot any when I looked:
>
> $ grep -r "PUBLIC\s*(\." --exclude-dir=build
>
> I guess it is possible, though. I'm not sure how I would properly handle
> it. Currently, covoar would just chop off everything after the ".", fail to
> find a coverage map, log an error, and move on.
>
> Do we think that is good enough?
>

Until we find a language where a user written method can have a dot in the
generated name. :)

>
> Alex
> _______________________________________________
> 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/20210316/2aa67cf6/attachment.html>