** Changed in: systemtap (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537125
Title:
ubuntu-14.04.04: fail to run systemt
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemtap (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537125
Title:
I see that symtab compile error when building a systemtap module which
uses userspace stack traces. A minimal example:
probe process.syscall {
print_usyms(ubacktrace());
}
Yields the following results when building:
username@mysecrethost:~/stap$ sudo stap -v -c /bin/ls clock.stp
P
That's on xenial, 16.04, systemtap 2.9-2ubuntu2 and uname -a:
Linux mysecrethost 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Tags removed: severity-critical
** Tags added: severity-high
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537125
Title:
ubuntu-14.04.04: fail to run systemtap test suites
To manage notificatio
> I tested systemtap on latest ubuntu16.04 ,make check error and other
failures are not yet fixed.
it works fine for me, although i'm on x86 so you may be seeing a
ppc64-specific failure?
# uname -a
Linux systemtap 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:17:28 UTC 2016
x86_64 x86_64 x86_64
> /usr/share/systemtap/runtime/linux/print.c:242:20: error: ?struct module? has
> no member named ?module_core?
> THIS_MODULE->module_core,
...
> root@ubuntu:~/systemtap-2.9# uname -a
> Linux ubuntu 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:06:23 UTC 2016
> ppc64le ppc64le ppc64le GNU/Linux
** Tags removed: severity-high
** Tags added: severity-critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537125
Title:
ubuntu-14.04.04: fail to run systemtap test suites
To manage notificatio
On Wed, Feb 24, 2016 at 07:57:55AM -, Launchpad Bug Tracker wrote:
> This bug was fixed in the package elfutils - 0.165-3ubuntu1
>
> ---
> elfutils (0.165-3ubuntu1) xenial; urgency=medium
>
> * Fix finding the debug info for Ubuntu kernels (Mark Wielaard). LP:
> #1537125.
Just
This bug was fixed in the package elfutils - 0.165-3ubuntu1
---
elfutils (0.165-3ubuntu1) xenial; urgency=medium
* Fix finding the debug info for Ubuntu kernels (Mark Wielaard). LP:
#1537125.
-- Matthias Klose Fri, 19 Feb 2016 16:57:49 +0100
** Changed in: elfutils (Ubuntu)
** Also affects: elfutils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537125
Title:
ubuntu-14.04.04: fail to run systemtap test suites
To man
Ravi, systemtap can pass through the $SYSTEMTAP_DEBUGINFO_PATH variable
to elfutils, which controls where debuginfo files are sought. If you
can get a working $SYSTEMTAP_DEBUGINFO_PATH set by hand, we can plop
that definition into systemtap proper.
--
You received this bug notification because y
** Tags removed: severity-critical
** Tags added: severity-high
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537125
Title:
ubuntu-14.04.04: fail to run systemtap test suites
To manage notificatio
On Tue, Jan 26, 2016 at 01:03:48AM -, Frank Ch. Eigler wrote:
> Hi -
> > I have just tested with the systemtap 2.9 package presently in xenial,
> > and the following test case fails the same way there as with systemtap
> > 2.3 in trusty:
> > # stap -v -e 'probe vfs.read {printf("read performe
Hi -
> I have just tested with the systemtap 2.9 package presently in xenial,
> and the following test case fails the same way there as with systemtap
> 2.3 in trusty:
>
> # stap -v -e 'probe vfs.read {printf("read performed\n"); exit()}'
> [...]
> semantic error: while resolving probe point: ide
> For ubuntu 14.04.03, systemtap 2.3 worked because it has a older kernel and
> older
> systemtap. Its no more the case now. The systemtap version needs to be
> upgraded.
I have just tested with the systemtap 2.9 package presently in xenial,
and the following test case fails the same way there a
> 9. apply systemtap fixes
> see BZ - https://bugzilla.linux.ibm.com/show_bug.cgi?id=131220
Please test with the actual systemtap package from trusty-proposed
(2.3-1ubuntu1.3), instead of manually patching the source.
> make check
This is not being run at build time because it is too intrusive o
** Package changed: ubuntu => systemtap (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537125
Title:
ubuntu-14.04.04: fail to run systemtap test suites
To manage notifications about this b
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
19 matches
Mail list logo
