From: "penguin-kernel@i-love.sakura.ne.jp" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/21811] New: Java probe crashes upon null argument.
Date: Fri, 21 Jul 2017 11:13:00 -0000 [thread overview]
Message-ID: <bug-21811-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=21811
Bug ID: 21811
Summary: Java probe crashes upon null argument.
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: penguin-kernel@i-love.sakura.ne.jp
Target Milestone: ---
Description of problem:
While testing RHEL 7.4 beta's systemtap-3.1-3.el7.src.rpm package, I noticed
that
Java VM always crashes upon trying to probe some Java methods. I wondered why,
but
it turned out that, as of 8be03508058fbbf2 ("new example:
sizeof_interactive.stp"),
we are not yet ready to handle null argument.
Steps to reproduce:
(1) Create Class1.java as below and compile it and run it as usual.
---------- Class1.java ----------
public class Class1 {
private static void method1(String obj) { }
public static void main(String args[]) throws Exception {
System.in.read();
method1(null);
}
}
---------- Class1.java ----------
# javac Class1.java
# java -cp . Class1
(2) Start SystemTap probe as below.
# SYSTEMTAP_VERBOSE=1 stap -e 'probe
java("Class1").class("Class1").method("method1(String)") { println(arg1); }'
(3) Press Enter key at java process so that method1 with null argument is
called.
Expected result:
SystemTap probe should show something like "(null)".
Actual result:
Java VM crashes due to SIGSEGV.
Version information:
# rpm -q byteman
byteman-2.0.4-5.el7.noarch
# rpm -q java-1.7.0-openjdk
java-1.7.0-openjdk-1.7.0.141-2.6.10.1.el7_3.x86_64
# stap -V
Systemtap translator/driver (version 3.2/0.166, commit
release-3.1-137-g8be03508058f + changes)
Copyright (C) 2005-2017 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
tested kernel versions: 2.6.18 ... 4.11
enabled features: JAVA PYTHON2 NLS NSS READLINE
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2017-07-21 11:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 11:13 penguin-kernel@i-love.sakura.ne.jp [this message]
2017-07-21 17:57 ` [Bug runtime/21811] " fche at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-21811-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).