From: Pratyush Anand <panand@redhat.com>
To: William Cohen <wcohen@redhat.com>
Cc: David Long <dave.long@linaro.org>, systemtap@sourceware.org
Subject: Re: Recent aarch64 kprobes and uprobes patch systemtap testing
Date: Wed, 16 Dec 2015 05:22:00 -0000 [thread overview]
Message-ID: <20151216052229.GH4674@dhcppc13.redhat.com> (raw)
In-Reply-To: <566B019D.1000309@redhat.com>
On 11/12/2015:12:02:21 PM, William Cohen wrote:
>
> The "FAIL: pthread_stacks -Gsize (0 0)" looks like it could be an issue with uprobes affecting the running of the program. Pratyush are you able to run this systemtap test locally?
Even when I run this test locally it does not work, but it fails very early in
my case. May be because of different libpthread.so
[root@amd-seattle-01 testsuite]# /root/bin/systemtap/bin/stap -gp4 ./systemtap.examples/process/threadstacks.stp -Gsize=65536 -d /root/systemtap/testsuite/pthread_stacks.x
semantic error: while resolving probe point: identifier 'process' at ./systemtap.examples/process/threadstacks.stp:17:7
source: probe process("/lib*/libpthread.so.*").function("allocate_stack") {
^
semantic error: no match
Pass 2: analysis failed. [man error::pass2]
[root@amd-seattle-01 testsuite]# ls /lib*/libpthread.so.*
/lib64/libpthread.so.0
[root@amd-seattle-01 testsuite]# ll /lib64/libpthread.so.0
lrwxrwxrwx. 1 root root 18 Dec 13 23:42 /lib64/libpthread.so.0 -> libpthread-2.17.so
[root@amd-seattle-01 testsuite]# objdump -d /lib64/libpthread.so.0 | grep allocate_stack
0000000000006a50 <__deallocate_stack>:
6a7c: 54000061 b.ne 6a88 <__deallocate_stack+0x38>
6a84: 35ffff83 cbnz w3, 6a74 <__deallocate_stack+0x24>
6a88: 540005e1 b.ne 6b44 <__deallocate_stack+0xf4>
6a90: 350005e0 cbnz w0, 6b4c <__deallocate_stack+0xfc>
6ac4: 350005e2 cbnz w2, 6b80 <__deallocate_stack+0x130>
6b14: 54000328 b.hi 6b78 <__deallocate_stack+0x128>
6b2c: 35ffffc2 cbnz w2, 6b24 <__deallocate_stack+0xd4>
6b34: 5400014c b.gt 6b5c <__deallocate_stack+0x10c>
6b48: 17ffffd1 b 6a8c <__deallocate_stack+0x3c>
6b58: 17ffffcf b 6a94 <__deallocate_stack+0x44>
6b74: 17fffff1 b 6b38 <__deallocate_stack+0xe8>
6b7c: 17ffffe7 b 6b18 <__deallocate_stack+0xc8>
6b8c: 17ffffe3 b 6b18 <__deallocate_stack+0xc8>
6c3c: 97ffff85 bl 6a50 <__deallocate_stack>
7ce4: 97fffb5b bl 6a50 <__deallocate_stack>
7f04: 97fffad3 bl 6a50 <__deallocate_stack>
894c: 97fff841 bl 6a50 <__deallocate_stack>
[root@amd-seattle-01 testsuite]#
~Pratyush
next prev parent reply other threads:[~2015-12-16 5:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 20:24 William Cohen
2015-12-10 21:12 ` David Long
2015-12-11 4:19 ` Pratyush Anand
2015-12-11 4:43 ` David Long
2015-12-11 17:02 ` William Cohen
2015-12-16 5:22 ` Pratyush Anand [this message]
2015-12-16 13:14 ` William Cohen
2015-12-17 0:53 ` Pratyush Anand
2015-12-11 20:59 ` William Cohen
2015-12-16 11:55 ` Pratyush Anand
2015-12-16 13:10 ` William Cohen
2015-12-10 21:17 ` David Long
2015-12-11 17:23 ` David Smith
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=20151216052229.GH4674@dhcppc13.redhat.com \
--to=panand@redhat.com \
--cc=dave.long@linaro.org \
--cc=systemtap@sourceware.org \
--cc=wcohen@redhat.com \
/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).