[Bug runtime/20131] New: listing_mode.exp wildcard library path failures

["dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>]

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

            Bug ID: 20131
           Summary: listing_mode.exp wildcard library path failures
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: dsmith at redhat dot com
  Target Milestone: ---

For a long while now, listing_mode.exp has had lots of failures. Commit 79be36d
improves the situation by making the test be more forgiving about 'stap -l'
output. There were times the test was expecting a full library path in the
output where 'stap -l' was outputting a relative path.

Originally, we were getting the following test numbers:

rhel6: 747 passes / 728 failures / 60 untested
rhel7: 899 passes / 792 failures / 36 untested
f23:   899 passes / 792 failures / 36 untested

With commit 79be36d, I'm getting:

rhel6: 1279 passes / 184 failures / 72 untested
rhel7: 1431 passes / 260 failures / 36 untested
f23:   1431 passes / 260 failures / 36 untested

So, where are the remaining failures coming from? Some are coming from bug
#18083 (listing_mode.exp fails on rhel6), related to line number problems.

The majority however are related to the following bug. At some point the
finding libraries using a wildcard stopped working, such as the following
command:

# stap -l process.library("*liblisting_mode.so").function("*") -c listing_mode

The function stap_list_cmd_lib in listing_mode.exp tries to find libraries 4
different ways: using a simple name ('.library("liblisting_mode.so")'), using a
relative name ('.library("./liblisting_mode.so")'), using the full path to the
library ('.library("/FOO/BAR/liblisting_mode.so")'), and using a wildcard
('.library("*liblisting_mode.so")'). Only the last variant fails.

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