This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/18769] New: [ppc64BE/--dyninst] unknown operator @__compat_task
- From: "mcermak at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Tue, 04 Aug 2015 08:03:47 +0000
- Subject: [Bug tapsets/18769] New: [ppc64BE/--dyninst] unknown operator @__compat_task
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=18769
Bug ID: 18769
Summary: [ppc64BE/--dyninst] unknown operator @__compat_task
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: mcermak at redhat dot com
Target Milestone: ---
Commit 7a563a0 added @__compat_task macro to
/usr/share/systemtap/tapset/powerpc/registers.stp. The commit is correct, but
it causes couple of failures in --dyninst mode on rhel7 ppc64. Thing is that in
dyninst mode /usr/share/systemtap/tapset/linux/syscalls.stpm, which defines
that macro, isn't being parsed.
This doesn't happen on x86_64, since this macro isn't used within
/root/mcermak-systemtap/systemtap-build/share/systemtap/tapset/x86_64/registers.stp
(but should be).
What solves the issue for me is symlinking syscalls.stpm to the ../dyninst
directory.
--
You are receiving this mail because:
You are the assignee for the bug.