fix issue with stacktrace_windows not allocating sufficient memory fo… #334
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…r SYMBOL_INFO struct
We encountered an issue in a private code base where printing out the stack after an error would itself cause an access violation in debug builds on Windows. The issue ends up being that the SYMBOL_INFO struct was constructed with insufficient memory to store the symbol name, which far exceeded the allocated amount of memory.
The issue is resolved by allocating more stack memory to allow for the use of up to MAX_SYM_NAME characters in the name field.