From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31400 invoked by alias); 1 Apr 2011 01:35:13 -0000 Received: (qmail 31341 invoked by uid 22791); 1 Apr 2011 01:35:12 -0000 X-SWARE-Spam-Status: No, hits=-6.0 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, 01 Apr 2011 01:35:01 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p311Z08p030575 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 31 Mar 2011 21:35:00 -0400 Received: from [10.3.113.54] (ovpn-113-54.phx2.redhat.com [10.3.113.54]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p311Z0t4010110; Thu, 31 Mar 2011 21:35:00 -0400 Message-ID: <4D952BC4.3010207@redhat.com> Date: Fri, 01 Apr 2011 01:35:00 -0000 From: Josh Stone User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.9 MIME-Version: 1.0 To: Zhiwei Ying CC: systemtap Subject: Re: too many transport failure References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: 2011-q2/txt/msg00001.txt.bz2 On 03/31/2011 05:40 PM, Zhiwei Ying wrote: > pp() will print a long string, thought that consumes a lot of buffer. > Does systemtap has a ppid(), only print the function address? And > provide a map between ppid() and pp() offline, so I can restore the > pp() information offline. Beware, there actually is a ppid(), but it means "parent process ID". Do you really need the complete source information that pp() gives? It would save a lot of bandwidth to use probefunc() in the .call probes, just as you have in the .return probes. You could get the raw probe address with a function like this: function REG_IP:long() %{ THIS->__retvalue = CONTEXT->regs ? REG_IP(CONTEXT->regs) : 0; %} Then, we don't have any automatic way to associate that to a pp(), but you could manually save that in a global array and print them all in an end probe as a translation key for some post-processing script. Josh