This bug was fixed in the package systemtap - 1.3-2ubuntu2
---
systemtap (1.3-2ubuntu2) natty; urgency=low
* Added upstream patches for kernels 2.6.37/2.6.38, identified after
running testsuite (LP: #721771)
-- Frederic Turgis f-tur...@ti.com Thu, 17 Mar 2011 12:25:48 +
By running testsuite on ARM, I have identified a set of upstream patches
for 2.6.37 kernel + new fixes from Redhat for 2.6.38 when we mentioned
our test results on their mailing list. Will submit new package
v1.4 issue is understood as a wrong management of .note.gnu.build-id
section in linker
** Branch linked: lp:~f-turgis/ubuntu/natty/systemtap/systemtap.2.6.38
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/721771
Title:
natty: systemtap incompatible with kernel
--
ubuntu-bugs mailing
was about to enter the same defect, tested on arm architecture. I faced the
error: ‘param_ops_int64_t’ undeclared here (not in a function) and also
applied redhat fix. The scripts I tested after were essentially home-made,
related to scheduler context switches, v4l2 monitoring, ... while using
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/721771
Title:
natty: systemtap incompatible with kernel
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Because systemtap package does not declare the dependecy on the kernel
debug info correctly, obviously apport-bug has not included the relevant
info either. But yes I have correct kernel debug info installed:
ii linux-image-2.6.38-4-generic-dbgsym 2.6.38-4.31
Linux kernel debug image for
Commit 75a48ca3 mentioned in the upstream bug report applies cleanly to
the systemtap source in natty and solves the problem with
error: ‘param_ops_int64_t’ undeclared here (not in a function)
I tried 2 simple system tap scripts: 1 succeeded and 1 failed. The new error is:
error:
The second problem
error: 'CLONE_STOPPED’ undeclared here (not in a function)
is fixed by upstream commit b30b7ed1.
All my tests are successful for the moment (that doesn't tell much, I
have used only very simple scripts)
--
You received this bug notification because you are a member of
