mcermak at redhat dot com | 22 Jul 12:33 2014

[Bug releng/17191] New: upstream head systemtap doesn't build on el6 (license issue)

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

            Bug ID: 17191
           Summary: upstream head systemtap doesn't build on el6 (license
                    issue)
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: releng
          Assignee: systemtap at sourceware dot org
          Reporter: mcermak at redhat dot com

Systemtap efa3ced fails to build (make rpm) on el6. Presumably caused by
91c82d369 (plus related 876abb05). This is el6 specific:

RPM build errors:
    File must begin with "/": GPLv2+
    File must begin with "/": COPYING

Please, fix.

--

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

dsmith at redhat dot com | 21 Jul 20:36 2014

[Bug translator/17190] New: 'stap -l' output not useful as stap input

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

            Bug ID: 17190
           Summary: 'stap -l' output not useful as stap input
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
          Assignee: systemtap at sourceware dot org
          Reporter: dsmith at redhat dot com

While working on bug #17140, I came across this. 

First use 'stap -l' to get a listing of function probe points:

====
# stap -l 'kernel.function("z* <at> mm/*.c").call'
kernel.function("zap_huge_pmd <at> mm/huge_memory.c:1412").call
kernel.function("zap_page_range <at> mm/memory.c:1401").call
kernel.function("zap_page_range_single <at> mm/memory.c:1427").call
kernel.function("zap_vma_ptes <at> mm/memory.c:1455").call
kernel.function("zone_absent_pages_in_node <at> mm/page_alloc.c:4506").call
kernel.function("zone_balanced <at> mm/vmscan.c:2675").call
kernel.function("zone_batchsize <at> mm/page_alloc.c:4061").call
kernel.function("zone_dirty_ok <at> mm/page-writeback.c:344").call
kernel.function("zone_pcp_reset <at> mm/page_alloc.c:6178").call
kernel.function("zone_pcp_update <at> mm/page_alloc.c:6172").call
kernel.function("zone_reclaimable_pages <at> mm/vmscan.c:150").call
(Continue reading)

jistone at redhat dot com | 19 Jul 00:18 2014

[Bug testsuite/17182] New: sdt_misc V3_uprobe --types failure

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

            Bug ID: 17182
           Summary: sdt_misc V3_uprobe --types failure
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: systemtap at sourceware dot org
          Reporter: jistone at redhat dot com

When trying to access "$arg1->a", sdt_misc errors:

semantic error: type definition 'test_probe_4_arg1' not found in
'[...]/testsuite/sdt_misc_V3_uprobe_types.x': identifier '$arg1' at
<input>:1:161

The test executable debuginfo indeed doesn't have any such type.  It seems that
"dtrace --types" was supposed to add a typedef, but since commit d3adcb4a23c3d
that option is noted obsolete and ignored.

--

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

dsmith at redhat dot com | 18 Jul 21:31 2014

[Bug runtime/17181] New: systemtap has problems attaching to resumed processes

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

            Bug ID: 17181
           Summary: systemtap has problems attaching to resumed processes
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: dsmith at redhat dot com

Systemtap will error when attempting to attach to a resumed process. This
happens with "fake" utrace (seen on RHEL7 and f20).

====
# stap -v -e 'probe syscall.getpid { printf("%s\n", probefunc()) }'
<snip>
Pass 5: starting run.
sys_getpid
<snip>
ERROR: utrace_set_events returned error -114 on pid 1903
WARNING: /usr/bin/staprun exited with status: 1
Pass 5: run completed in 0usr/70sys/8196real ms.
Pass 5: run failed.  [man error::pass5]
====

Here's how to reproduce this one:

(Continue reading)

dsmith at redhat dot com | 18 Jul 18:56 2014

[Bug tapsets/17178] New: syscall/nd_syscall test failures on f20

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

            Bug ID: 17178
           Summary: syscall/nd_syscall test failures on f20
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tapsets
          Assignee: systemtap at sourceware dot org
          Reporter: dsmith at redhat dot com

On f20 (3.15.4-200.fc20.x86_64), the following are new syscall/nd_syscall
testsuite failures:

FAIL: 32-bit getsockopt nd_syscall
FAIL: 32-bit setsockopt nd_syscall
FAIL: 32-bit getsockopt syscall
FAIL: 32-bit select syscall
FAIL: 32-bit setsockopt syscall

From some debugging, the getsockopt() failures are happenning because
getsockopt() has been moved under socketcall().

--

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

(Continue reading)

Hemant Kumar | 17 Jul 07:53 2014
Picon

[PATCH v2 0/3] perf/sdt : Support for SDT markers

This patchset helps in listing dtrace style markers(SDT) present in user space
applications through perf.
Notes/markers are placed at important places by the
developers. They have a negligible overhead when not enabled.
We can enable them and probe at these places and find some important information
like the arguments' values, etc.

We have lots of applications which use SDT markers today, like:
Postgresql, MySql, Mozilla, Perl, Python, Java, Ruby, libvirt, QEMU, glib

To add SDT markers into user applications:
We need to have this header sys/sdt.h present.
sys/sdt.h used is version 3.
If not present, install systemtap-sdt-devel package (for fedora-18).

Please refer to the Documentation patch to see how the SDT markers are added into
a program.

With this patchset,
- Use perf to list the markers in the app:
# perf list sdt ./user_app

./user_app :
%user_app:foo_start
%user_app:fun_start

- Also, we can see the SDT markers present in our system in the usual binaries.
These usual binaries are libraries (dsos) listed by ldconfig --print-cache and some
binaries present in PATH environment variable.

(Continue reading)

David Smith | 17 Jul 23:14 2014
Picon

systemtap/pcp integration

Here's a small update on the prototype systemtap/pcp integration work
I'm doing. I've create a systemtap branch, called 'dsmith/mmv' that
contains all my work. Basically this work allows systemtap to create
'mmv' memory mapped files.

If you checkout and build that, then you should be able to run the
attached systemtap script. This script is a translation of pcp's example
python mmv script found in src/python/mmv.py.

Note that systemtap will create a file called 'mmv' in
/proc/systemtap/{MODULE_NAME}. I've just been using pcp's 'mmvdump'
utility to dump the contents of the /proc/systemtap/{MODULE_NAME}/mmv
file. Currently the pcp mmv pmda only looks in one place for mmv files,
but it might be possible to create a symbolic link to systemtap's mmv
file to make it happy.

The code works for the attached script, but I'm sure it is quite
fragile. Things like locking, error checking, documentation, etc. need
to be done.

--

-- 
David Smith
dsmith <at> redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)
global inst0, inst1, counter_metric, instant_metric, indom_metric
(Continue reading)

dsmith at redhat dot com | 17 Jul 18:27 2014

[Bug dyninst/16795] utrace_p5.exp leaves stapdyn processes running

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

David Smith <dsmith at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dsmith at redhat dot com

--- Comment #2 from David Smith <dsmith at redhat dot com> ---
On f20 (3.15.4-200.fc20.x86_64), I'm seeing a problem with the
pthreadprobes.exp testcase and dyninst. One of the dyninst tests causes the
test executable to get stuck. In order to get the test to proceed I have to
manually kill the test executable. This may (or may not) be related to the
problems mentioned in this bug report.

--

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

dsmith at redhat dot com | 14 Jul 15:54 2014

[Bug testsuite/17155] New: systemtap.examples/profiling/functioncallcount.stp failures on x86_64

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

            Bug ID: 17155
           Summary: systemtap.examples/profiling/functioncallcount.stp
                    failures on x86_64
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: systemtap at sourceware dot org
          Reporter: dsmith at redhat dot com

When I run the systemtap.examples/check.exp testcase (which tests all the
examples), the functioncallcount.stp example fails about half the time on
x86_64. When it fails, I see this in systemtap.log:

====
ERROR: probe overhead exceeded threshold
WARNING: Number of errors: 1, skipped probes: 0
WARNING: /usr/local/bin/staprun exited with status: 1
Pass 5: run failed.  [man error::pass5]
child process exited abnormally
RC 1
FAIL: systemtap.examples/profiling/functioncallcount run
====

The guts of functioncallcount.stp look like:

(Continue reading)

dsmith at redhat dot com | 10 Jul 16:59 2014

[Bug runtime/17140] New: systemtap.examples/profiling/functioncallcount.stp causing kernel panic on s390x

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

            Bug ID: 17140
           Summary: systemtap.examples/profiling/functioncallcount.stp
                    causing kernel panic on s390x
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: dsmith at redhat dot com
              Host: s390x

On RHEL7 (3.10.0-123.el7.s390x), when I run the following command:

====
# stap -v ../src/testsuite/systemtap.examples/profiling/functioncallcount.stp
"* <at> mm/*.c" -c "sleep 1"
Pass 1: parsed user script and 103 library script(s) using
143240virt/28188res/3092shr/25540data kb, in 130usr/20sys/442real ms.
WARNING: function mem_init is in blacklisted section: keyword at
../src/testsuite/systemtap.examples/profiling/functioncallcount.stp:7:1
 source: probe kernel.function( <at> 1).call {  # probe functions listed on
commandline
         ^
WARNING: function paging_init is in blacklisted section: keyword at :7:1
 source: probe kernel.function( <at> 1).call {  # probe functions listed on
commandline
(Continue reading)

ajakop at redhat dot com | 8 Jul 18:07 2014

[Bug runtime/17131] New: process(PID).{function, plt, mark} does not limit probe to specified process

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

            Bug ID: 17131
           Summary: process(PID).{function, plt, mark} does not limit
                    probe to specified process
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: ajakop at redhat dot com

Running a script of the format 'process(PID).{function, plt, mark}' does not
seem to limit the probe to the specified process. Instead it probes any process
running the same program as the specified process.

--

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


Gmane