This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/14026] inode-uprobes should compute proper SET_REG_IP before probe invocation
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Wed, 15 Aug 2012 14:08:57 +0000
- Subject: [Bug runtime/14026] inode-uprobes should compute proper SET_REG_IP before probe invocation
- Auto-submitted: auto-generated
- References: <bug-14026-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14026
--- Comment #30 from David Smith <dsmith at redhat dot com> 2012-08-15 14:08:57 UTC ---
(In reply to comment #28)
> (In reply to comment #27)
> > The 3 failures are all prelink failures, of the form:
> >
> > ====
> > prelink failed: /usr/sbin/prelink: Could not set security context for
> > ./libuprobeslibgcc-O3-m64-prelink-sep-debug-after.so: Operation not supported
> > ====
>
> Is that on NFS? I believe that case has a bug (either kernel/selinux or
> prelink).
Yes, this was on NFS.
> You might want to try testsuite/systemtap.context/uprobe_uaddr.exp which should
> test this case more precisely.
I get the same results with and without the patch. Looking at the test, it
uses uretprobes, which of course don't work with inode uprobes.
====
Running ../../src/testsuite/systemtap.context/uprobe_uaddr.exp ...
FAIL: uprobe_uaddr (0)
FAIL: uprobe_uaddr match line 0 main+*
FAIL: uprobe_uaddr match line 1 func+*
FAIL: uprobe_uaddr match line 2 func2+*
FAIL: uprobe_uaddr match line 3 func+*
FAIL: uprobe_uaddr match line 4 main+*
=== systemtap Summary ===
# of expected passes 1
# of unexpected failures 6
====
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.