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:
![Image](https://private-user-images.githubusercontent.com/9502098/406517704-bae590ef-1567-400e-9a47-2795558178d5.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk5NjQ1MDQsIm5iZiI6MTczOTk2NDIwNCwicGF0aCI6Ii85NTAyMDk4LzQwNjUxNzcwNC1iYWU1OTBlZi0xNTY3LTQwMGUtOWE0Ny0yNzk1NTU4MTc4ZDUucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTlUMTEyMzI0WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NGNiNWY5NTllNjk1NDNhNWRhNTAxM2FlMzY3MTkxZGRjNmMxYmE1YWRmMWVhYTMyYTM2NDFiN2NkZDQ0OWViMiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.K4zr3O3Uh9FwfjRBCZXpCJHOKJ8oTyknQugm9dzPDm0)
The same code with
![Image](https://private-user-images.githubusercontent.com/9502098/406517980-effffd28-ca2b-469a-bebe-2c16d762a62d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk5NjQ1MDQsIm5iZiI6MTczOTk2NDIwNCwicGF0aCI6Ii85NTAyMDk4LzQwNjUxNzk4MC1lZmZmZmQyOC1jYTJiLTQ2OWEtYmViZS0yYzE2ZDc2MmE2MmQucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTlUMTEyMzI0WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YjE5OWU2MDZkODQ5ZWM0ZjZkYjI0OTZiZDhhNjNhZmUyZGQ3YWVhNDQ0ZjM0NjI5OGFkMDg5NGYxOWY3OWEzMSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.BbodVudj4R8Vv_DVinadUaxOawOQAEpZ8HwgFQOlrJM)
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: