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

[Stefan Karlsson]

On Mon, 23 Sep 2024 04:36:32 GMT, David Holmes <dholmes at openjdk.org> wrote:

> > I was trying to convey that it might be better to rewrite the calling code to perform its own checks / logging instead of relying on a "low-level" assert in Thread.
> 
> The calling code is of course being fixed (or at least the cause dealt with one way or another). The point here was to simply enhance the existing assertion to be more informative for the next time it gets triggered.

Right. And that was what I was curious to know more about because I think there would be better ways to get better diagnostics by changing code there. Anyways, I'll leave you to deal with that in a separate issue.

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

PR Comment: https://git.openjdk.org/jdk/pull/21102#issuecomment-2367506165