-
Bug
-
Resolution: Fixed
-
P1
-
9
-
None
-
gcc 4.8.1
-
b24
-
x86_64
-
linux
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8056567 | emb-9 | Unassigned | P1 | Resolved | Fixed | b24 |
Configure a slowdebug build on Linux with gcc 4.8.1
Debug java, setting a breakpoint at (say) FieldReassigner::do_field
run some complex piece of Java (it needs to do some deoptimization for this case;
this example is listed because it is known-bad because that is what I was debugging
when I hit this; I think I've seen others before) hit a breakpoint, go "up", and say:
(gdb) p fields_sorted
$3 = <optimized out>
this is wrong for "slowdebug".
If instead the code is compiled with -O0 instead of -Og, you will see
(gdb) p fields_sorted
$1 = (int *) 0x7fff000038d0
Workaround: use find+grep to locate every instance of -Og in the .make, .sh, and .m4 files, replace with -O0, and reconfigure for a slowdebug build.
Debug java, setting a breakpoint at (say) FieldReassigner::do_field
run some complex piece of Java (it needs to do some deoptimization for this case;
this example is listed because it is known-bad because that is what I was debugging
when I hit this; I think I've seen others before) hit a breakpoint, go "up", and say:
(gdb) p fields_sorted
$3 = <optimized out>
this is wrong for "slowdebug".
If instead the code is compiled with -O0 instead of -Og, you will see
(gdb) p fields_sorted
$1 = (int *) 0x7fff000038d0
Workaround: use find+grep to locate every instance of -Og in the .make, .sh, and .m4 files, replace with -O0, and reconfigure for a slowdebug build.
- backported by
-
JDK-8056567 gcc/g++ -Og is harmful to the debugging experience.
-
- Resolved
-
- relates to
-
-
- Resolved
-
-
-
- Resolved
-
-
JDK-8032045 Enable compiler and linker safety switches for debug builds
-
- Resolved
-