Re: kernel read fault when accessing context variables

[tonyg362 <tonyg3622@yahoo.com>]

Thanks for your help, the sched_switch trace point seems like a good option
and works fine on my machine. I just really wanted to get it to work the
other way if for no other reason than I spent so much time trying to get it
to work, I may keep trying. Funny thing is that I can get my original script
working on an embedded ARM 9 running Ubuntu 9.10 but I can't get it on my
PC. :-/

-Tony


Mark Wielaard-4 wrote:
> 
> On Thu, 2010-07-08 at 21:11 -0700, tonyg362 wrote:
>> That's strange, I have tried probing at every line in the scheduler and
>> get a
>> semantic error or a kernel read fault. Can you tell me your setup and how
>> you built your debug kernel?
> 
> That result was against the rhel6 beta kernel on x86_64:
> http://www.redhat.com/rhel/beta/
> 
> But the same work on i686 against the fedora 13 (2.6.33.5-124.fc13.i686)
> kernel. The source line moved a bit, so I had to use +44 here for
> kernel.statement("schedule@kernel/sched.c+44") also the trace point just
> works out of the box kernel.trace("sched_switch").
> 
> Cheers,
> 
> Mark
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/kernel-read-fault-when-accessing-context-variables-tp29099754p29117808.html
Sent from the Sourceware - systemtap mailing list archive at Nabble.com.