RFR: 8340491: Thread stack-base assertion should report which thread has the un-set stack [v2]

[David Holmes]

> Please review this simple enhancement to an assertion so we can identify which thread had the problem.
> 
> I had to move the function to the cpp file due to include file issues.
> 
> We are limited in what we can print due to this being used very early in the thread initialization process - in particular no ResourceMarks are possible so we can't print the name.
> 
> Testing:
>  - tier 5 (used to debug [JDK-8340401](https://bugs.openjdk.org/browse/JDK-8340401))
>  - tiers 1-3 sanity
> 
> Thanks

David Holmes has updated the pull request incrementally with one additional commit since the last revision:

  Keep inline version for release builds

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

Changes:
  - all: https://git.openjdk.org/jdk/pull/21102/files
  - new: https://git.openjdk.org/jdk/pull/21102/files/e6358a57..c887fdfa

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=21102&range=01
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=21102&range=00-01

  Stats: 3 lines in 2 files changed: 2 ins; 0 del; 1 mod
  Patch: https://git.openjdk.org/jdk/pull/21102.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/21102/head:pull/21102

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