Unfortunately, we were not able to reproduce the problem based on the description you provided.
If VisualGDB behaves differently than you expect, please share the steps to reproduce the problem per our problem reporting guidelines and we will try to investigate this further.