[Bug runtime/18083] New: listing_mode.exp fails on rhel6

["mcermak at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

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

            Bug ID: 18083
           Summary: listing_mode.exp fails on rhel6
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: mcermak at redhat dot com

Created attachment 8168
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8168&action=edit
test logs

Commit e93efe2d0 (eliminate gcc5 warnings) introduced listing_mode.exp
failures. Some of them were later eliminated by commit 06902e9a6 (Adapt to
changed line numbers). Currently (at the f94683c76 time) some failures still
remain. Looking at the *first* failure in the x86_64 el6 log I see something
that looks like a real systemtap bug.

=======
executing: stap -l process.function("main").label("main_label")  -c
listing_mode
received:
"process("/root/mcermak-systemtap/systemtap/testsuite/listing_mode").function("main@./systemtap.base/listing_mode.c:37").label("main_label")"
expected:
"^process\("/root/mcermak-systemtap/systemtap/testsuite/listing_mode"\)\.function\("main@[^:]+:33"\)\.label\("main_label"\)$"
FAIL: listing_mode (process.function("main").label("main_label")  -c
listing_mode)
=======

The label actually *is* on line 33 in the test program, but line 37 refers to
it too:

=======
 29 int main(void) {
 30 
 31    globalvar = foo(globalvar);
 32    globalvar = libfoo(globalvar);
 33 main_label:
 34    STAP_PROBE1(main, mark, globalvar);
 35    while (1) {sleep(5000);}
 36    return 0;
 37    if (0) goto main_label;
 38 }
=======

So apparently systemtap reports wrong line number in this case.

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