stack overflow detection producing false positives

[biddisco]

I have bugs in my code that cause segfaults. however the new stack overflow detection is frequently producing messages such as
"Stack overflow in coroutine at address 0x000056036def3790"

I'm not sure if anything can be done about this, or if it is serious enough to fix - since a genuine stack-overflow might be indistinguishable from a silly memory access error. I'm reporting this just in case the stack overflow detection can be improved.

[hkaiser]

As far as I'm aware, @ct-clmsn is already working on finding a solution.

[ct-clmsn]

@hkaiser @biddisco on it - getting close to a preliminary solution. hope to have something debugged by the end of today.

[justwagle]

@diehlpk I think you can configure HPX with HPX_WITH_THREAD_STACKOVERFLOW_DETECTION=OFF.

[hkaiser]

We currently have two options: HPX_WITH_THREAD_STACKOVERFLOW_DETECTION and HPX_WITH_STACKOVERFLOW_DETECTION which is a bug.

[ct-clmsn]

@biddisco @hkaiser I'll be pushing a solution to merge for review this afternoon/evening. Still having issues getting a platform together that can be used to debug the work correctly. The "Ubuntu for Windows" environment has some issues that are making the stackoverflow detection a challenge to debug.

[hkaiser]

See #3016 and #3018 for fixes to the configuration mess.

[hkaiser]

This has been fixed by merging #3021