[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <alpine.LFD.2.00.0908251333410.6044@xanadu.home>
Date: Tue, 25 Aug 2009 13:37:37 -0400 (EDT)
From: Nicolas Pitre <nico@....org>
To: venki kaps <venkiece2005@...il.com>
Cc: "sagar.abhishek@...il.com" <sagar.abhishek@...il.com>,
"jkenisto@...ibm.com" <jkenisto@...ibm.com>,
"rmk+kernel@....linux.org.uk" <rmk+kernel@....linux.org.uk>,
"linux@....linux.org.uk" <linux@....linux.org.uk>,
"linux-arm@...r.kernel.org" <linux-arm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"prasanna@...ibm.com" <prasanna@...ibm.com>
Subject: Re: ARM + jprobes/kretprobes SEGV/hangs/OOPS in 2.6.29 kernel
On Tue, 25 Aug 2009, venki kaps wrote:
> Hi,
>
> I have been tracing kernel system call information using
> the Kprobes/jprobes/kretprobes implementation in the 2.6.29 kernel on
> ARM architecture.
> Although the mainline kprobe/jprobe/kretprobe examples are working
> fine (do_fork),
> I have been facing some issues while running my own jprobe/kretprobe tests.
>
[...]
>
> Query:
> =====
> - Are there any limitations for jptobes/kretporbes in mainline kernel for ARM?
No limitation in particular that I know of.
> - Why it works for only do_fork and why not for others
> (do_execve/sys_open/sys_close/sys_read/sys_write)?
I don't know. Will try to have a look.
> - Is it required any additional setup to achieve this?
Not supposed to need anything special.
Nicolas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists