Stepping into java.lang.String.<init> during the call of a
constructor with a String literal argument causes an invalid memory
reference in java_g.exe.
Sample Program:
public class BugDemo {
public static void main(String argv[]) {
String foo = new String("foo");
}
}
To illustrate this, enter the following commands in jdb:
load BugDemo
stop in BugDemo.main
run BugDemo
step
next
After the step, jdb indicates that the program is stopped in
java.lang.String.<init>, presumably to construct the String
corresponding to the literal "foo". If at this point, one enters a
next command, an invalid memory reference occurs in java_g.exe.
constructor with a String literal argument causes an invalid memory
reference in java_g.exe.
Sample Program:
public class BugDemo {
public static void main(String argv[]) {
String foo = new String("foo");
}
}
To illustrate this, enter the following commands in jdb:
load BugDemo
stop in BugDemo.main
run BugDemo
step
next
After the step, jdb indicates that the program is stopped in
java.lang.String.<init>, presumably to construct the String
corresponding to the literal "foo". If at this point, one enters a
next command, an invalid memory reference occurs in java_g.exe.
- duplicates
-
JDK-4046770 jdb dump command crashes while displaying static string
- Closed