8241043: Expand assertions to identify thread with errant _stack_base

Reviewed-by: mikael
This commit is contained in:
David Holmes 2020-03-16 02:16:49 -04:00
parent 4b978533ca
commit 95898e86a1
2 changed files with 2 additions and 1 deletions

View file

@ -349,6 +349,7 @@ void Thread::record_stack_base_and_size() {
// If possible, refrain from doing anything which may crash or assert since // If possible, refrain from doing anything which may crash or assert since
// quite probably those crash dumps will be useless. // quite probably those crash dumps will be useless.
set_stack_base(os::current_stack_base()); set_stack_base(os::current_stack_base());
assert(_stack_base != NULL, "current_stack_base failed for %s", name());
set_stack_size(os::current_stack_size()); set_stack_size(os::current_stack_size());
#ifdef SOLARIS #ifdef SOLARIS

View file

@ -748,7 +748,7 @@ protected:
public: public:
// Stack overflow support // Stack overflow support
address stack_base() const { assert(_stack_base != NULL,"Sanity check"); return _stack_base; } address stack_base() const { assert(_stack_base != NULL,"Sanity check failed for %s", name()); return _stack_base; }
void set_stack_base(address base) { _stack_base = base; } void set_stack_base(address base) { _stack_base = base; }
size_t stack_size() const { return _stack_size; } size_t stack_size() const { return _stack_size; }
void set_stack_size(size_t size) { _stack_size = size; } void set_stack_size(size_t size) { _stack_size = size; }