systemtap

https://sourceware.org/bugzilla/show_bug.cgi?id=20389 Bug ID: 20389 Summary: warn on $var.field when $var->field correct Product: systemtap Version: unspecified Status: NEW ... [More] Severity: normal Priority: P2 Component: translator Assignee: systemtap at sourceware dot org Reporter: fche at redhat dot com Target Milestone: --- I could've sworn we already have a warning for this, but can't find it: e.g.: stap -p4 -e ' probe kernel.function("__d_drop") { x=$dentry->d_lockref.count println(x) }' WARNING: never-assigned local variable 'count' (similar: x): identifier 'count' at :1:59 source: probe kernel.function("__d_drop") { x=$dentry->d_lockref.count println(x) } ^ semantic error: while processing probe kernel.function("__d_drop< at >fs/dcache.c:468") from: kernel.function("__d_drop") semantic error: 'struct lockref' is being accesse [Less]

Use our standard testsuite 'kill' procedure in several tests.

Use our standard testsuite 'kill' procedure in several tests.

Hi All, Not sure if this has been addressed before. Checked the archive and couldn't find a solution there. I tried user space probing with Systemtap 3.0. But it gives me the following error. $ sudo stap -e 'probe process("./h264ref").function("*") ... [More] { printf("hello\n"); }' ERROR: Couldn't insert module '/tmp/stapsPVPF2/stap_b964ab648506800b700ce82c4e1cf5cd_167937.ko': Unknown symbol in module WARNING: /usr/bin/staprun exited with status: 1 Pass 5: run failed. [man error::pass5] Tip: /usr/share/doc/systemtap/README.Debian should help you get started. My user account is in following groups. stapdev stapusr stapsys Kernel details $ uname -a Linux 3.19.0-28-generic #30~14.04.1-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux $grep CONFIG_UPROBES /boot/config-`uname -r` CONFIG_UPROBES=y Systemtap version $ stap --version Systemtap translator/driver (version 3.0/0.158, non-git sources) Copyright (C) 2005-2015 Red Hat, Inc. and others This is free software; see the source for copying conditions. enabled features [Less]

https://sourceware.org/bugzilla/show_bug.cgi?id=20377 Bug ID: 20377 Summary: stable functions converted to < at >const aren't optimized Product: systemtap Version: unspecified Status: ... [More] NEW Severity: normal Priority: P2 Component: translator Assignee: systemtap at sourceware dot org Reporter: jistone at redhat dot com Target Milestone: --- Although < at >const does specify /* stable */ underneath, that doesn't let the function containing it be treated as stable. We have quite a few tapset functions that were converted from full embedded-c to this < at >const form, and those have thus regressed in getting stable treatment. Consider tid(): $ stap -e 'probe oneshot { println(tid(), tid()) }' -v -p2 \ | sed -ne '/^begin/,$p' begin /* <- oneshot += begin <- oneshot */ { println(__global_tid__overload_0(), __global_tid__overload_0()); __global_exit__overload_0(); } Compare to ns_tid(), which didn't get converted to < at >co [Less]

Fix handling of internal transport flags.

Fix handling of internal transport flags.

Make sure the unprivileged_myproc.exp testcase kills its processes.

Make sure the unprivileged_myproc.exp testcase kills its processes.