You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In arrows/mvg/algo/initialize_cameras_landmarks.h, the initialize function gives a default value for the constraints parameter as nullptr. However, as far as I can tell actually calling the function with the default parameter will always result in a crash.
I'm unsure if the solution for this is to simply remove the default value for the constraints parameter, or if additional checks and cases for a value of nullptr are needed throughout the code called by the function. I believe the default value for the parameter was ported over from the arrows/mvg/algo/initialize_cameras_landmarks_basic.h file.
The text was updated successfully, but these errors were encountered:
Additional checks are needed. Anywhere we use pointer or shared_pointer we need to check that the pointer is not null before dereferencing it unless there was already an earlier check guaranteeing it was not null. The contraints are intended to be optional so null is valid input. Line 2440 and other places like it should start like this
In
arrows/mvg/algo/initialize_cameras_landmarks.h
, theinitialize
function gives a default value for theconstraints
parameter asnullptr
. However, as far as I can tell actually calling the function with the default parameter will always result in a crash.The
constraints
parameter will be passed intoinitialize_keyframes
, which will then pass it intometadata_centric_keyframe_initialization
, which will then reach reach line 2440, and crash.I'm unsure if the solution for this is to simply remove the default value for the
constraints
parameter, or if additional checks and cases for a value ofnullptr
are needed throughout the code called by the function. I believe the default value for the parameter was ported over from thearrows/mvg/algo/initialize_cameras_landmarks_basic.h
file.The text was updated successfully, but these errors were encountered: