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]

[Bug testsuite/16473] rlimit.exp: adjust for weak symbols


https://sourceware.org/bugzilla/show_bug.cgi?id=16473

--- Comment #4 from Jonathan Lebon <jlebon at redhat dot com> ---
Created attachment 7455
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7455&action=edit
rlimit.patch

Looking more closely into this, I think I have a better idea of what's going
on. During partial inlining, non-inlined bits are left in e.g. foo.part.0().
This function has no DWARF info associated with it (GCC PR44712 discusses
implementing this, but it doesn't seem like there's anything in yet). It does
however show up in the symtab.

Since assess_dbinfo_reqt() only sees a function_str, it deems that the symtab
should be investigated as well. So when we tell stap to list all the functions
matching e.g. "*ar*", we pick up both DWARF functions as well as symtab
functions matching this.

This causes things that require DWARF such as $$vars to not get resolved, which
then causes an error thrown later on during type resolution.

So the error is correct insomuch as stap did try to do its best in finding
matching functions. It could be argued that a better error message should be
output (e.g. "need DWARF information for this").

As for rlimit.exp, all we need is a simple patch that will cause
assess_dbinfo_reqt() to require DWARF info (see attached patch).

-- 
You are receiving this mail because:
You are the assignee for the bug.


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