From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-12771-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 6142 invoked by alias); 23 Jun 2009 14:21:48 -0000
Received: (qmail 6064 invoked by uid 48); 23 Jun 2009 14:21:37 -0000
Date: Tue, 23 Jun 2009 14:21:00 -0000
From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Message-ID: <20090623142132.10318.mjw@redhat.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug translator/10318] New: Bad address reading arg from mark probe
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-q2/txt/msg01015.txt.bz2

This is a continuation of bug #10289 comment #1:
> I don't yet have a test because this fix ends up failing with an unrelated
> problem: kernel read fault at 0xfffffffffffffe15 (addr) near identifier '$arg1'

This might or might not be related to bug #10305 where I see a failure to
resolve the arguments of a mark probe (after fixing the bias offsets that made
the finding of probes fail).

Stan, with which testcase did you see the above?

-- 
           Summary: Bad address reading arg from mark probe
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: mjw at redhat dot com
                CC: scox at redhat dot com


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

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