From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-20999-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 3107 invoked by alias); 23 Jul 2013 15:46:39 -0000
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
Received: (qmail 28375 invoked by uid 48); 23 Jul 2013 15:44:36 -0000
From: "lberk at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/15773] New: Java probing doesn't detect class/method validity
Date: Tue, 23 Jul 2013 15:46:00 -0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: systemtap
X-Bugzilla-Component: runtime
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lberk at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: systemtap at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-15773-6586@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-q3/txt/msg00044.txt.bz2

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

            Bug ID: 15773
           Summary: Java probing doesn't detect class/method validity
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: lberk at redhat dot com

When probing java methods, systemtap fails to report spelling errors in the
class or method names.  For example:

for the method foo.printMessage(int)

the (incorrect) probe point java(PID).class("foo").method("printmessage(int)")
would run with simply no ouput.

We should output an error that the method name should be "printMessage(int)".

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