-
Enhancement
-
Resolution: Fixed
-
P4
-
11, 12, 13, 14, 15
-
b23
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8314196 | 11.0.22-oracle | Daniel Skantz | P4 | Resolved | Fixed | b01 |
| JDK-8318952 | 8u411 | Daniel Skantz | P4 | Resolved | Fixed | b01 |
When debugging with gdb, one can use
(gdb) call C->print_method(PHASE_FAILURE, 0, 0)
to print the current method. This, however, requires that all flags for enabling the Ideal Graph Visualizer to print methods in general are set. Moreover, if C is not defined one must either go up the stack or use:
(gdb) call Compile::current()->print_method(PHASE_FAILURE, 0, 0)
which is tedious. This could be simplified with a debug method such that we only need to call with an optional custom phase name:
(gdb) call print_method(phase_name)
The above gdb calls do not work when debugging with rr [1]. This RFE should also provide a possibility to print methods on the fly while stepping through the code with rr.
[1] https://rr-project.org/
(gdb) call C->print_method(PHASE_FAILURE, 0, 0)
to print the current method. This, however, requires that all flags for enabling the Ideal Graph Visualizer to print methods in general are set. Moreover, if C is not defined one must either go up the stack or use:
(gdb) call Compile::current()->print_method(PHASE_FAILURE, 0, 0)
which is tedious. This could be simplified with a debug method such that we only need to call with an optional custom phase name:
(gdb) call print_method(phase_name)
The above gdb calls do not work when debugging with rr [1]. This RFE should also provide a possibility to print methods on the fly while stepping through the code with rr.
[1] https://rr-project.org/
- backported by
-
JDK-8314196 Simplify usage of Compile::print_method() when debugging with gdb and enable its use with rr
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Closed
-
-
JDK-8263775 C2: igv_print() crash unexpectedly when called from debugger
-
- Resolved
-
-
-
- Resolved
-