Hi,
Sorry, this looks like a bug of the gcc compiler and not a VisualGDB-specific issue.
Our best advice would be to try reproducing it in a command-line build (if you are using MSBuild, you can configure it via VS Project Properties to create a .bat file with all build commands) and try posting in the GCC mailing list.
Another option would be to try using the Keil or IAR compiler instead of GCC. VisualGDB supports both of them and they generally provide a better optimization than GCC, and come with their own support.