| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8083045 | emb-9 | Volker Simonis | P4 | Resolved | Fixed | b34 |
| JDK-8086392 | 8u65 | Volker Simonis | P4 | Resolved | Fixed | b01 |
| JDK-8068336 | 8u60 | Zoltan Majo | P4 | Resolved | Fixed | b01 |
| JDK-8137630 | emb-8u65 | Unassigned | P4 | Resolved | Fixed | b01 |
| JDK-8076667 | emb-8u60 | Volker Simonis | P4 | Resolved | Fixed | team |
It would be nice if we could make this functionality available from within gdb during debugging sessions.
This can be easily achieved by refactoring the corresponding code from VMError::report() in vmError.cpp into it own method in debug.cpp.
With another helper function which creates a frame object, we can then get a mixed stack trace in gdb as follows:
Linux/amd64
call pns(make_frame($sp, $rbp, $pc))
Linux/i586
call pns(make_frame($sp, $ebp, $pc))
Linux/ppc64
call pns(make_frame($sp, $pc))
- backported by
-
JDK-8068336 Refactor native stack printing from vmError.cpp to debug.cpp to make it available in gdb as well
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8072066 Need test to cover fix hs_err can contain incomplete stack trace
-
- Closed
-