RFR(S): 8211852: inspect stack during error reporting (original) (raw)
Doerr, Martin martin.doerr at sap.com
Mon Oct 8 12:54:36 UTC 2018
- Previous message: RFR(S): 8211714: Need to update vm_version.cpp to recognise VS2017 minor versions
- Next message: RFR(S): 8211852: inspect stack during error reporting
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
after making os::print_location more reliable, I'd like to use it to inspect the top of the stack, too (in a dedicated step).
We already inspect the registers during error reporting, but some important pointers may be only on stack, especially on architectures which don't have so many registers. Since hs_err files are often all we get after a crash, it is often valuable to spend a little space for more information about what's referenced on top of the stack.
I've uploaded my proposal here: http://cr.openjdk.java.net/~mdoerr/8211852_stack_info/webrev.00/
I had thought about using print_location in the platform specific code (print_context), but I think using a dedicated step is better. Especially if print_location doesn't work we'll still get the dump of the context which contains a piece of the stack as hex dump without any further inspection.
Please review.
Best regards, Martin
- Previous message: RFR(S): 8211714: Need to update vm_version.cpp to recognise VS2017 minor versions
- Next message: RFR(S): 8211852: inspect stack during error reporting
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]