From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30531 invoked by alias); 17 Jun 2011 18:43:37 -0000 Received: (qmail 30523 invoked by uid 22791); 17 Jun 2011 18:43:36 -0000 X-SWARE-Spam-Status: No, hits=-6.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 17 Jun 2011 18:43:15 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p5HIhFxN011629 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 17 Jun 2011 14:43:15 -0400 Received: from fche.csb (vpn-11-114.rdu.redhat.com [10.11.11.114]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p5HIhEio025704; Fri, 17 Jun 2011 14:43:14 -0400 Received: by fche.csb (Postfix, from userid 2569) id 22E305812E; Fri, 17 Jun 2011 14:43:13 -0400 (EDT) To: "Richard W.M. Jones" Cc: systemtap@sourceware.org Subject: Re: staprun -c deadlocks often References: <20110617154320.GC18438@amd.home.annexia.org> From: fche@redhat.com (Frank Ch. Eigler) Date: Fri, 17 Jun 2011 18:43:00 -0000 In-Reply-To: <20110617154320.GC18438@amd.home.annexia.org> (Richard W. M. Jones's message of "Fri, 17 Jun 2011 16:43:20 +0100") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: 2011-q2/txt/msg00302.txt.bz2 Hi, Richard - rjones wrote: > systemtap-1.4-9.fc15.x86_64 > kernel 2.6.38.7-30.fc15.x86_64 > > I'm not sure if I'm "doing it wrong" Nope, not your fault. > [...] Here is what I'm doing (as root): > stap -p4 \ > -e 'probe module("ext2").statement ("*@*.c:*") { printf ("%s\n", pp()); }' > [stap command prints the module name, used below] > staprun -o /tmp/stap -c /bin/ls /home/rjones/.systemtap/cache/44/stap_44fe38ee6f62656645948ce5d275d678_260427.ko Just running stap .... -c /bin/ls should give the same results. Or are you cross-compiling? (If so, there are other methods available that wouldn't require hand-copying and hand-running staprun.) > As I say, more often than half the time, instead of printing out a > directory listing, the staprun command will just hang. [...] This sounds like http://sourceware.org/PR10189, where too many warning messages interfere with non-warning staprun<->module packets. - FChE