From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23561 invoked by alias); 9 Jul 2010 17:27:51 -0000 Received: (qmail 23552 invoked by uid 22791); 9 Jul 2010 17:27:50 -0000 X-SWARE-Spam-Status: No, hits=1.1 required=5.0 tests=AWL,BAYES_00,DKIM_ADSP_CUSTOM_MED,FORGED_YAHOO_RCVD,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,SPF_HELO_PASS,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Received: from kuber.nabble.com (HELO kuber.nabble.com) (216.139.236.158) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 09 Jul 2010 17:27:46 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1OXHMW-0005Ir-Ax for systemtap@sourceware.org; Fri, 09 Jul 2010 10:27:44 -0700 Message-ID: <29117808.post@talk.nabble.com> Date: Fri, 09 Jul 2010 17:27:00 -0000 From: tonyg362 To: systemtap@sourceware.org Subject: Re: kernel read fault when accessing context variables In-Reply-To: <1278660467.2409.6.camel@hermans.wildebeest.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <29099754.post@talk.nabble.com> <1278599298.1040.18.camel@springer.wildebeest.org> <29108946.post@talk.nabble.com> <1278621720.22525.7.camel@springer.wildebeest.org> <1278622338.22525.11.camel@springer.wildebeest.org> <29114046.post@talk.nabble.com> <1278660467.2409.6.camel@hermans.wildebeest.org> X-IsSubscribed: yes Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2010-q3/txt/msg00051.txt.bz2 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.