This is the mail archive of the
mailing list for the systemtap project.
Re: [PATCH v4 1/3] systemtap/tapsets.cxx: Fix dwarfless probes on multiple static functions
- From: Mark Wielaard <mjw at redhat dot com>
- To: Hemant Kumar <hemant at linux dot vnet dot ibm dot com>
- Cc: systemtap at sourceware dot org, naveen dot n dot rao at linux dot vnet dot ibm dot com, ulrich dot weigand at de dot ibm dot com, uweigand at gcc dot gnu dot org, anton at samba dot org, fche at redhat dot com
- Date: Thu, 23 Apr 2015 16:21:31 +0200
- Subject: Re: [PATCH v4 1/3] systemtap/tapsets.cxx: Fix dwarfless probes on multiple static functions
- Authentication-results: sourceware.org; auth=none
- References: <1429525764-23471-1-git-send-email-hemant at linux dot vnet dot ibm dot com> <1429710017 dot 1938 dot 71 dot camel at bordewijk dot wildebeest dot org> <5537B1CA dot 8030302 at linux dot vnet dot ibm dot com>
On Wed, 2015-04-22 at 20:05 +0530, Hemant Kumar wrote:
> On 04/22/2015 07:10 PM, Mark Wielaard wrote:
> > @@ -8242,6 +8242,8 @@ symbol_table::purge_syscall_stubs()
> > if (!addrs || addrs->empty())
> > return;
> > /* Highly unlikely that multiple symbols named "sys_ni_syscall" may exist */
> > + if (addrs->size() > 1)
> > + cerr << _("Multiple 'sys_ni_syscall' symbols found.");
> > Dwarf_Addr stub_addr = addrs->front();
> > Just so that if this highly unlikely scenario does occur we get a
> > warning something is fishy.
> Right! looks good.
And I am glad we did add that warning.
Martin found it triggered on ppc64be (ELFv1 ABI).
It was caused by ppc64be using function descriptors and stap using both
the actual function entry symbol .sys_ni_syscall and the function
descriptor symbol sys_ni_syscall. Both resolved to the same address. And
we mangle the name of the function entry symbol to remove the leading
dot. So they also have the same name.
This was mostly harmless. But it showed some inefficiencies. Frank
solved the immediate issue by using address sets instead of lists, so
duplicate addresses are just not returned:
Author: Frank Ch. Eigler <email@example.com>
Date: Wed Apr 22 16:53:51 2015 -0400
tapsets.cxx: fix symbol/address lookup returned-data to sets passed
The symbol_table lookup_symbol[_address] functions are safer if they
return their result-sets by value rather than by pointer. The latter
in specific should be a set rather than a list, to properly eliminate
Then I removed the hardcoded #ifdef __powerpc__ constructs in
tapsets.cxx and replaced them with a check of whether the target is
ppc64 ELFv1 abi. That way cross-stapping (is that a word?) should work
across arches too (but I haven't tested that, just that ppc64be and
ppc64le both work correctly). This also removes the actual duplicates,
so the maps aren't filled with extra func_infos (there could be lots of
duplicates in the kernel when using function descriptors).
Author: Mark Wielaard <firstname.lastname@example.org>
Date: Thu Apr 23 15:59:49 2015 +0200
ppc64le doesn't have function descriptors. Remove __powerpc__ in
Only process the opd section and do function descriptor mangling when
the target is ppc64 ELFv1 ABI. Also filter out any duplicate
When seeing a symbol with a name starting with '.' we assume it is a
regular function pointer and not a pointer to a function descriptor
and mangle its name. That might create duplicates if there is also a
function descriptor with that name (the address will already have been
resolved to the same address).