ajakop at redhat dot com | 25 Feb 23:26 2015

[Bug translator/16974] excessive context size after {stmt;}->stmt; optimization

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

Abe Jakop <ajakop at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ajakop at redhat dot com
         Resolution|---                         |FIXED

--- Comment #1 from Abe Jakop <ajakop at redhat dot com> ---
fixed in commit: d74a787413c860f3ee9624e73db6f7e046d67420

--

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

dsmith at redhat dot com | 25 Feb 16:52 2015

[Bug tapsets/18026] New: timerfd_create, timerfd_gettime, timerfd_settime syscall support needs to be added

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

            Bug ID: 18026
           Summary: timerfd_create, timerfd_gettime, timerfd_settime
                    syscall support needs to be added
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tapsets
          Assignee: systemtap at sourceware dot org
          Reporter: dsmith at redhat dot com

In the following kernel commit, support for the timerfd() syscall was added (in
kernel 2.6.22):

====
commit b215e283992899650c4271e7385c79e26fb9a88e                                 
Author: Davide Libenzi <davidel <at> xmailserver.org>                                
Date:   Thu May 10 22:23:16 2007 -0700                                          

    signal/timer/event: timerfd core                                            
====

Then in the following kernel commit, support for timerfd() was removed and
instead the timerfd_create(), timerfd_gettime(), timerfd_settime() syscalls
were added (in kernel 2.6.25):

====
(Continue reading)

Josh Stone | 23 Feb 22:48 2015
Picon

PSA: stap triggers an internal error in ld 2.24.90

Some pre-2.25 binutils ld, called 2.24.90 on Debian Jessie and Ubuntu
Utopic, have a regression that appears to be quite easily triggered by
stap kernel modules.  It was fixed before the final binutils 2.25.  You
can see an example in stap PR14226, comment 13 and on:

https://sourceware.org/bugzilla/show_bug.cgi?id=14226#c13

ld: BFD (GNU Binutils for Ubuntu) 2.24.90.20141014 internal error,
aborting at ../../bfd/elf-eh-frame.c line 1727 in
_bfd_elf_write_section_eh_frame

ld: Please report this bug.

Debian has bug #769067 which says it's fixed in 2.24.90.20141111-2.  But
AFAICT Jessie is still on 2.24.90.20141023-1, so I suspect it's still
broken.  I don't know Debian procedure, but I guess this bug should be
copied to jessie, so the fix can be backported.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769067

Ubuntu Utopic has 2.24.90.20141014-0ubuntu3.1, which was still found to
be broken today by "rrva" on irc.  I was going to file a bug, but
launchpad said, "Bad bot, go away!"  So... someone else who is not
thought to be a bot should probably follow up with them.

Thanks,
Josh

Nathan Scott | 20 Feb 06:09 2015
Picon

[PATCH] python3 support for /usr/bin/dtrace

Hi all,

Came across a few syntax issues when building PCP with static
probes enabled on a system where python3 was default.  Patch
below gets me to a working build again.

cheers.

--
Nathan

Use python syntax in dtrace.in that works for python v3 also

A series of syntax errors result if /usr/bin/dtrace is run on
a python3 system, such as:

  File "/usr/bin/dtrace", line 190
    except ParseException, err:
                         ^
SyntaxError: invalid syntax

The downside to this change is that python versions before 2.6
may no longer work, but that seems to be a fairly common minimum
python version these days.

diff --git a/dtrace.in b/dtrace.in
index aa51d57..564cf0a 100644
--- a/dtrace.in
+++ b/dtrace.in
 <at>  <at>  -187,12 +187,12  <at>  <at>  class _PypProvider(_HeaderCreator):
(Continue reading)

curzonj at gmail dot com | 19 Feb 23:50 2015

[Bug translator/18001] New: Using backtrace(), caller(), or callers(n) causes a gcc internal error

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

            Bug ID: 18001
           Summary: Using backtrace(), caller(), or callers(n) causes a
                    gcc internal error
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
          Assignee: systemtap at sourceware dot org
          Reporter: curzonj at gmail dot com

Overview: Calling caller() causes a gcc internal error.
Reproduce:

stap -k -v -e 'probe kernel.function("dev_hold") { printf("%s", caller()) }'

Actual Results: GCC internal error during compile.
Expected Results: Compile happens and script runs

I want to use caller, but I tried callers(n) and backtrack() and they caused
the same GCC internal error result.

The compile log and artifacts are here:
https://gist.github.com/curzonj/857090762c52730aa028

root <at> vagrant-ubuntu-trusty-64:/vagrant# uname -a
Linux vagrant-ubuntu-trusty-64 3.13.0-45-generic #74-Ubuntu SMP Tue Jan 13
(Continue reading)

dsmith at redhat dot com | 19 Feb 17:24 2015

[Bug translator/18000] New: kernel tracepoints not found without using the cache

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

            Bug ID: 18000
           Summary: kernel tracepoints not found without using the cache
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
          Assignee: systemtap at sourceware dot org
          Reporter: dsmith at redhat dot com

On 3.18.3-201.fc21.x86_64 with HEAD systemtap, I'm seeing this:

====
# rm -rf ~/.systemtap/cache
# stap --disable-cache -p4 -e 'probe kernel.trace("net_dev_queue") { exit() }'
semantic error: while resolving probe point: identifier 'kernel' at <input>:1:7
        source: probe kernel.trace("net_dev_queue") { exit() }
                      ^

semantic error: no match

Pass 2: analysis failed.  [man error::pass2]
# stap -p4 -e 'probe kernel.trace("net_dev_queue") { exit() }'
/home/dsmith/.systemtap/cache/32/stap_32123f202c07308478d5a4b63bd3f3fb_1013.ko
====

So, if you disable the cache, the net_dev_queue tracepoint cannot be found. The
(Continue reading)

Abe Jakop | 18 Feb 22:19 2015
Picon

SystemTap 2.7 release

The SystemTap team announces release 2.7, RedGrizzlyCoffee!

  Kernel tracepoint subsystem probes, optimized string passing, syscall tapset
  improvements, highlighted educational examples, addr->file:line mapping,
  SystemTap's 10th anniversary, and more!

= Where to get it

  https://sourceware.org/systemtap/ - our project page
  https://sourceware.org/systemtap/ftp/releases/systemtap-2.7.tar.gz
  https://koji.fedoraproject.org/koji/packageinfo?packageID=615
  git tag release-2.7 (commit bf16266782e1f25)

  There have been over 290 commits since the last release.
  There have been over 35 bugs fixed / features added since the last release.

= How to build it

  See the README and NEWS files at
  https://sourceware.org/git/?p=systemtap.git;a=tree

  Further information at https://sourceware.org/systemtap/wiki/

= SystemTap's 10th Anniversary

  February 12 was the 10th anniversary of SystemTap. We would to thank all of
  our contributors over the years, listed below.

  Aaron Tomlin, Abegail Jakop, Adrien Kunysz, Alexander Lochmann,
  Alexander Y. Fomichev, Alfred Landrum, Ananth N Mavinakayanahalli,
(Continue reading)

mcermak at redhat dot com | 16 Feb 18:24 2015

[Bug runtime/17986] New: unprivileged_myproc.exp and unprivileged_probes.exp regressed on el6 (systemtap-2.5-5.el6 versus release-2.6-274-gbabad5b31b70)

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

            Bug ID: 17986
           Summary: unprivileged_myproc.exp and unprivileged_probes.exp
                    regressed on el6 (systemtap-2.5-5.el6 versus
                    release-2.6-274-gbabad5b31b70)
           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 8134
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8134&action=edit
release-2.6-274-gbabad5b31b70 logs showing the failures

The unprivileged_myproc.exp and unprivileged_probes.exp testcases regressed on
el6 (systemtap-2.5-5.el6 versus release-2.6-274-gbabad5b31b70).

Attaching x86_64 logs to demonstrate the issue. Reference logs for 2.5-5.el6
can be found at https://url.corp.redhat.com/2305d37.

--

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

(Continue reading)

mcermak at redhat dot com | 16 Feb 17:39 2015

[Bug runtime/17985] New: babad5b31b systemtap.pass1-4/buildok.exp regressed on el6 compared to systemtap-2.5-5.el6

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

            Bug ID: 17985
           Summary: babad5b31b systemtap.pass1-4/buildok.exp regressed on
                    el6 compared to systemtap-2.5-5.el6
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: mcermak at redhat dot com

Well, this is not a "real" regression, since what fails is new subtest
netfilter-glob.stp which wasn't there in 2.5-5.el6.

 6.7 S i686 # stap -up4 -e 'probe netfilter.** {next}'
cc1: warnings being treated as errors
/tmp/stappF3ryq/stap_e3d6183624e3f7d07097d952ff49f9f5_281081_src.c: In function
‘function___read4’:
/tmp/stappF3ryq/stap_e3d6183624e3f7d07097d952ff49f9f5_281081_src.c:8676: error:
cast to pointer from integer of different size
/tmp/stappF3ryq/stap_e3d6183624e3f7d07097d952ff49f9f5_281081_src.c:8676: error:
cast to pointer from integer of different size
/tmp/stappF3ryq/stap_e3d6183624e3f7d07097d952ff49f9f5_281081_src.c:8676: error:
cast to pointer from integer of different size
/tmp/stappF3ryq/stap_e3d6183624e3f7d07097d952ff49f9f5_281081_src.c: In function
‘function___read_char’:
/tmp/stappF3ryq/stap_e3d6183624e3f7d07097d952ff49f9f5_281081_src.c:8715: error:
(Continue reading)

mcermak at redhat dot com | 16 Feb 15:37 2015

[Bug runtime/17983] New: SEGV in bz6850.exp (f20/i686)

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

            Bug ID: 17983
           Summary: SEGV in bz6850.exp (f20/i686)
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: mcermak at redhat dot com

bz6850.exp causes SEGV on f20/i686

=======
f20 i686 # stap -V | head -n 1
Systemtap translator/driver (version 2.7/0.161, commit
release-2.6-274-gbabad5b31b70 + changes)
f20 i686 # uname -r 
3.18.6-100.fc20.i686+PAE
f20 i686 # gcc systemtap.base/bz6850.c  -g -o bz6850
f20 i686 # stap  -e 'probe process("./bz6850").function("*").return {exit()}'
-c './bz6850' 
WARNING: function _start return probe is blacklisted: keyword at <input>:1:1
 source: probe process("./bz6850").function("*").return {exit()}
         ^
WARNING: Child process exited with signal 11 (Segmentation fault)
WARNING: /usr/bin/staprun exited with status: 1
Pass 5: run failed.  [man error::pass5]
(Continue reading)

mcermak at redhat dot com | 16 Feb 10:10 2015

[Bug runtime/17982] New: rlimit.exp stalls on f20

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

            Bug ID: 17982
           Summary: rlimit.exp stalls on f20
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: mcermak at redhat dot com

Following rlimit.exp subtest causes stall on f20:

as_non_root su -s /bin/sh nobody -c "SYSTEMTAP_DIR=/tmp/.systemtap-nobody
/usr/bin/stap --rlimit-stack=1 --rlimit-stack=999999999999 -wp4
./systemtap.base/rlimit.stp"

--

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


Gmane