Calling std::abort()
yields unusable stacktrace in Windows 10 Release builds
#1126
Open
1 of 3 tasks
Description
Calling
std::abort()
yields unusable stacktrace in Windows 10 Release buildsWhen does the problem happen
Environment
/MD
/DEBUG
/O2
+/Ob2
Steps To Reproduce
When run in Release build, this code yields a mostly unusable and seemingly incorrect stack trace:
The same code with
throw std::runtime_error("abort")
instead ofstd::abort()
yields a usable stack trace:In Debug build, both types of errors yield a usable stack trace
Our Runtime Library flag is
/MD
in the Release build and/MDd
in Debug buildLog output
The text was updated successfully, but these errors were encountered: