Not true.
A segmentation violation is a common symptom of undefined behaviour (typically due to your program modifying memory it shouldn't).
More often than not, code which causes undefined behaviour is distinct from code where the symptoms are detected. Adding or removing a line, and having symptoms disappear, therefore often indicates that some code BEFORE the offending line is the cause of the problem.
All you are doing by commenting out that particular line is removing the code where the symptoms become visible. You are not affecting the cause of the problem.
Indeed. You have demonstrated laziness in this thread in more ways that assuming untested code is valid.