From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-13342-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 14504 invoked by alias); 29 Aug 2009 00:49:44 -0000
Received: (qmail 14475 invoked by uid 48); 29 Aug 2009 00:49:33 -0000
Date: Sat, 29 Aug 2009 00:49:00 -0000
From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Message-ID: <20090829004933.10574.jistone@redhat.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug tapsets/10574] New: Some functions resolve to pc=0x0
X-Bugzilla-Reason: AssignedTo
Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <systemtap.sourceware.org>
List-Subscribe: <mailto:systemtap-subscribe@sourceware.org>
List-Post: <mailto:systemtap@sourceware.org>
List-Help: <mailto:systemtap-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: systemtap-owner@sourceware.org
X-SW-Source: 2009-q3/txt/msg00493.txt.bz2

We resolve actually quite a few functions to a null pc:

$ stap -l 'process("/usr/bin/stap").function("*")' -vv 2>&1 | grep pc=0x0 | wc -l
1917

These null pcs get carried all the way into the stap_uprobe_specs array.  It
doesn't seem to have any ill effect at runtime, but it's doubtful that probes at
offset 0 in a module are of any use.

Depending on the root cause, we should either skip over these null addresses, or
search further for what the real entrypc should be.

-- 
           Summary: Some functions resolve to pc=0x0
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tapsets
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: jistone at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=10574

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.