Integrated: 8340491: Thread stack-base assertion should report which thread has the un-set stack

[David Holmes]

On Fri, 20 Sep 2024 02:25:19 GMT, David Holmes <dholmes at openjdk.org> wrote:

> 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

This pull request has now been integrated.

Changeset: 31858fc4
Author:    David Holmes <dholmes at openjdk.org>
URL:       https://git.openjdk.org/jdk/commit/31858fc4107a616aefd785cc06e932d1f03e2697
Stats:     11 lines in 2 files changed: 10 ins; 0 del; 1 mod

8340491: Thread stack-base assertion should report which thread has the un-set stack

Reviewed-by: shade, kevinw, stefank

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

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