-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dump resources: remove calls to exit(1) #1852
base: dev
Are you sure you want to change the base?
Conversation
CI gfxreconstruct build queued with queue ID 291996. |
CI gfxreconstruct build # 5250 running. |
CI gfxreconstruct build # 5250 passed. |
@@ -1879,7 +1879,6 @@ VkResult VulkanReplayDumpResourcesBase::QueueSubmit(const std::vector<VkSubmitIn | |||
GFXRECON_LOG_ERROR("Dumping draw calls failed (%s). Terminating.", | |||
util::ToString<VkResult>(res).c_str()) | |||
Release(); | |||
exit(1); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing these means that the message is no longer true. But the message probably means that execution can't continue. Doesn't this need to terminate somehow, either by abort
or throw
or some such?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, probably GFXRECON_LOG_FATAL, I think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at framework/util/logging.h
, it seems there is no real difference between GFXRECON_LOG_ERROR
and GFXRECON_LOG_FATAL
. Do we want FATAL
to terminate every time?
Fixes #1761 |
f92eaa5
to
b190353
Compare
CI gfxreconstruct build queued with queue ID 306822. |
CI gfxreconstruct build # 5354 running. |
CI gfxreconstruct build # 5354 passed. |
No description provided.