From: William Cohen <wcohen@redhat.com>
To: David Long <dave.long@linaro.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
"systemtap@sourceware.org" <systemtap@sourceware.org>
Subject: Re: Segmenation fault for systemtap tests using the arm uprobes support
Date: Wed, 06 Nov 2013 15:25:00 -0000 [thread overview]
Message-ID: <527A5F1F.6060000@redhat.com> (raw)
In-Reply-To: <527986F9.7030204@linaro.org>
On 11/05/2013 07:02 PM, David Long wrote:
> On 11/05/13 15:36, William Cohen wrote:
>> On 10/29/2013 04:50 PM, David Long wrote:
>>> OK, I've seen your error once now. I guess I just need to run the test a number of times looking for it. I am investigating.
>>>
>>> -dl
>>>
>>
>> Hi David,
>>
>> I finally got the uprobe-v2 branch of https://git.linaro.org/gitweb?p=people/davelong/linux.git;a=summary working on my samsung arm chromebook (needed to use a newer exynos5250-snow.dtb file). I reran the at_var test with the newer kernel and do not see the sigsegv.
>>
>> I am going to rerun the test tests with this kernel and see if the problem went away with the newer version of the patches.
>>
>> -Will
>>
>
>
> I'm still seeing the SEGV with my latest patches on V3.12 on a Panda.
>
> -dl
>
Hi David,
With the uprobe-v2 version I only saw one test that appeared to fail because of a sigsegv:
FAIL: 32_BIT_UTRACE_SYSCALL_ARGS
I have uploaded the test results of the systemtap run with the uprobes-v2 branch to the systemtap dejazilla system:
web.elastic.org/~dejazilla/viewsummary.php?summary=%3D%27%3C527A58AC.9000301%40redhat.com%3E%27
dejazilla allows comparison between different systemtap.sum files. I looked through the list of recent arm7l runs:
https://web.elastic.org/~dejazilla/viewsummary.php?_offset=0&_limit=20&_sort=1A&summary=&age=&rg=&tool=&variant=%3D%27armv7l-unknown-linux-gnueabihf%27&versions=&pass=&fail=&kpass=&kfail=&xpass=&xfail=&untested=&unresolved=&unsupported=&warning=&error=
The following URL is a comparison between the older uprobes and uprobes-v2 runs:
https://web.elastic.org/~dejazilla/viewrgdiff.php?rg1=150513&rg2=822815&_sort=0A&_limit=1000
Some of the like minidebuginfo and process_by_cmd2.stp passed with the uprobes-v2 kernel.
When searching for ways to test uprobes support I cam across https://github.com/rabinv/uprobes-test . Are these tests useful or have they been orphaned?
-Will
next prev parent reply other threads:[~2013-11-06 15:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5229DF78.4060301@redhat.com>
[not found] ` <5229E091.1090802@linaro.org>
[not found] ` <52681E03.8080509@redhat.com>
[not found] ` <52701F7A.8070102@linaro.org>
2013-11-05 20:36 ` William Cohen
2013-11-06 0:02 ` David Long
2013-11-06 15:25 ` William Cohen [this message]
2013-11-06 15:57 ` David Long
2013-11-06 16:33 ` William Cohen
2013-11-08 18:24 ` David Long
2013-11-22 2:12 ` William Cohen
2013-11-22 2:42 ` David Long
2013-11-26 5:25 ` David Long
2013-11-26 21:06 ` William Cohen
2013-11-27 16:23 ` Results for arm uprobes-v3 posted William Cohen
2013-11-27 16:26 ` David Long
2013-11-27 16:44 ` William Cohen
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=527A5F1F.6060000@redhat.com \
--to=wcohen@redhat.com \
--cc=dave.long@linaro.org \
--cc=naresh.kamboju@linaro.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).