Thread: Problem with vector iterator

Originally Posted by grumpy

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.

You are right. However, I really meant that that line is the entry point for understanding the problem, i.e. you read that line, and that gives you the information on where to proceed from there.
I was trying to get everyone to focus on that line to start with, thus the reason for those earlier words.

I've learned that sometimes making untrue statements helps all those involved reach the real truth of a matter. Has something to do with the way our brains think...

Btw, I read up on segfaults before even starting this thread, but still did not spot the problem. I didn't realize it was the fault of the < operator of the S_browser struct.

Indeed. You have demonstrated laziness in this thread in more ways that assuming untested code is valid.

I wont dispute that point. lol