From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/12748] need syscall-number database in tapset
Date: Fri, 24 Jun 2016 15:40:00 -0000 [thread overview]
Message-ID: <bug-12748-6586-bPZWWuJfYA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12748-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=12748
--- Comment #11 from Martin Cermak <mcermak at redhat dot com> ---
Created attachment 9361
--> https://sourceware.org/bugzilla/attachment.cgi?id=9361&action=edit
proposed patch
One more update fixing the i686 issue. This patch was tested also on Fedora
i686 and got updated accordingly. I've been trying to add support for ia64
too, but although stap builds with devtoolset-2-gcc-4.8.2-15.1.el5 recompiled
for ia64 (-w), the resulting systemtap modules do not reasonably kbuild on
rhel5. I skipped this. Attached patch was tested on all the platforms
available to me.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-06-24 15:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 21:02 [Bug tapsets/12748] New: " fche at redhat dot com
2016-06-09 15:26 ` [Bug tapsets/12748] " mcermak at redhat dot com
2016-06-20 15:26 ` mcermak at redhat dot com
2016-06-20 15:31 ` mcermak at redhat dot com
2016-06-20 18:07 ` dsmith at redhat dot com
2016-06-20 18:22 ` dsmith at redhat dot com
2016-06-20 18:25 ` dsmith at redhat dot com
2016-06-21 8:42 ` mcermak at redhat dot com
2016-06-21 18:41 ` dsmith at redhat dot com
2016-06-23 14:53 ` mcermak at redhat dot com
2016-06-23 15:02 ` dsmith at redhat dot com
2016-06-24 13:11 ` mcermak at redhat dot com
2016-06-24 15:40 ` mcermak at redhat dot com [this message]
2016-06-28 12:30 ` mcermak at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-12748-6586-bPZWWuJfYA@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).