This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: DWARF Information not Used with Wildcards


Hi Torsten,

On Mon, 2018-04-23 at 21:48 +0200, Torsten Polle wrote:
> Am 22.04.2018 um 22:44 schrieb Mark Wielaard <mark@klomp.org>:
> > Are you sure this is the DIE that describes the function in
> > dwflpp::resolve_prologue_endings? I am surprised since this is just the
> > prototype of the function and has no associated address at all. I would
> > expect a subprogram or inlined_subroutine that has at least a range (if
> > not a low/high_pc).
> 
> This is all I could find. I did a grep for „xpc_dictionary_create_compat“.
> Checked with objdump and normal readelf as well. The result is the same.

Aha, yes, it probably is the only one named that way. But other dies
will probably reference it as their abstract_origin or specification.
You can get the actual DIE used with something like:

      clog << "function '" << it->name << "', DIE offset: "
           << hex << dwarf_dieoffset (& it->die) << endl;

> > Also could you show the producer attribute of the CU DIE?
> > I wonder which version of GCC you are using (or some other
> > compiler).
> 
> It’s GCC: GNU C99 6.2.0 -m64 -march=core2 -msse3 -mtune=generic
> -mfpmath=sse -msgxx-glibc -g -O2 -std=gnu11 -std=gnu99 -ffunction-
> sections -fdata-sections -feliminate-unused-debug-types -fpic

I wonder if it is the -ffunction-sections -feliminate-unused-debug-
types that triggers the issue for you.

It doesn't really matter now though, since I believe we found the
underlying issue. I was just curious why I couldn't replicate it.

Thanks,

Mark


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]