Bug 15773 - Java probing doesn't detect class/method validity
Summary: Java probing doesn't detect class/method validity
Status: NEW
Alias: None
Product: systemtap
Classification: Unclassified
Component: runtime (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-23 15:44 UTC by Lukas Berk
Modified: 2016-05-27 16:34 UTC (History)
3 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Berk 2013-07-23 15:44:36 UTC 
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)".
Comment 1 Lukas Berk 2014-02-18 15:35:29 UTC 
It may be possible to use the javap tool (the java class file disassembler) to achieve this.  Official documentation can be found at: http://docs.oracle.com/javase/7/docs/technotes/tools/windows/javap.html