RFR: 8294160: misc crash dump improvements

[Dean Long]

Try to recover and output meaningful information in more situations, such as:
- when a pointer is in Method metadata memory range, but the memory is not committed
- when we call a bad address

When calling a bad address, we usually don't get a meaningful stack backtrace, but in many situations we can if we know where to find the caller information.

-------------

Commit messages:
 - windows x86
 - linux x86 print_instructions
 - revert
 - linux aarch64 support, simplify x86
 - better crash dumps, linux x86

Changes: https://git.openjdk.org/jdk/pull/10387/files
 Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=10387&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8294160
  Stats: 29 lines in 6 files changed: 20 ins; 2 del; 7 mod
  Patch: https://git.openjdk.org/jdk/pull/10387.diff
  Fetch: git fetch https://git.openjdk.org/jdk pull/10387/head:pull/10387

PR: https://git.openjdk.org/jdk/pull/10387