I really like the idea of visualGDB but my now probably out of date experience was a bit disappointing...
about a year and a half ago I used it for a project that had both a cortex-m part, and an embedded Linux part.. we had the $300ish visual gdb license.
it worked for both parts of the project, which was impressive, but seemed a bit weird, and not quite complete. Menus didn't make sense for the cortex m project, and multiple people across the project using all kinds of different computers had crashing issues with the clang intellisense plugin which would crash the whole visual studio ide regularly...
I *would* be interested to try again as the developers seemed pretty keen, and if they have been continuing to develop since then, I'd expect they will have progressed a lot.
Biggest gotcha for getting too attached to visualGDB as a commercial tool is the Visual Studio community license... Once your team gets too big, you can't use community any more, and then you're in paid VS land, which is pretty expensive, and you could just as well afford any of the other commercial embedded IDEs..