-
Notifications
You must be signed in to change notification settings - Fork 614
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
add check for nullptr handle in body track c++ shutdown()
#1373
Comments
Hi. I prefer to leave it open. I verify fixes for all the bugs that I open and aren't closed (against my wishes). I have so many open issues, that I must have tools (like open github issues) to manage them. This allows somewhat the better phase changes of: open -> resolved -> closed. |
Fixed in v1.1.1. |
@qm13, Fixed in what version? For customers to verify unseeable code changes, we need to know the exact version in which is was potentially fixed so that customers can verify, escalate non-fix, etc. |
The
k4abt::shutdown()
api doesn't check itsm_handle
before calling the C apik4abt_tracker_shutdown()
. This is a minor inconsistency as compared to its siblingk4abt::shutdown()
which does check its handle withif (m_handle != nullptr)
.Ask
I request the handle test be added to
k4abt::shutdown()
so to be in alignment with its siblingshutdown()
and remove boilerplate from user code.Fix
Add the handle test to the C++ body track header like the following. While it is not necessary, I also added
const
to the function signature since it does not modify the class variables.Alternatives
In a scenario of serial shutdown and destroy...
User code can use a one line if test
if (bodyTracker) bodyTracker.shutdown(); bodyTracker.destroy();
The text was updated successfully, but these errors were encountered: