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: Fri, 22 Nov 2013 02:12:00 -0000 [thread overview]
Message-ID: <528EBD68.9040904@redhat.com> (raw)
In-Reply-To: <527D2971.9040103@linaro.org>
On 11/08/2013 01:12 PM, David Long wrote:
> On 11/06/13 11:33, William Cohen wrote:
>> On 11/06/2013 10:57 AM, David Long wrote:
>>> On 11/06/13 10:24, William Cohen wrote:
>>>>
>>>> Hi David,
>>>>
>>>> With the uprobe-v2 version I only saw one test that appeared to fail because of a sigsegv:
>>>>
>>>
>>> Are you testing on the same hardware? It's conceivable that could make a difference, especially if the number of CPU's is different.
>>>
>>
>
> I wouldn't expect those options to make a difference for uprobes. They might for kprobes.
>
> I just finally found the bug in ARM uretprobe's. It's a simple fix.
>
> -dl
>
Hi Dave,
Are there updated ARM uprobe-v3 patches somewhere? I would be happy to try them. out.
-Will
next prev parent reply other threads:[~2013-11-22 2:12 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
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 [this message]
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=528EBD68.9040904@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).