My setup:

1. Debug symbols are stripped from the executable before deploying to target
2. Run symbol-file <exe.debug> at the beginning when deploying.

I’m trying to speed up the overall process of debug/deploy, and step #2 usually takes 4-5 seconds on my target device.  Normally, I don’t expect bad things to happen, so, I came up with an idea:  don’t do step 2 until the breakpoint or assert hits.

Issues with this idea:

1. After the breakpoint hits, I call symbol-file. The Call Stack window is still grayed out.  However, if I go the Thread window and switched threads, the Call Stack is now lit, and with the correct function names.  Would be nice if it gets updated automatically.
2. When I double-click an entry in the Call Stack, I still get the “Source not available:  Frame not in module window”.  However, if I do a bt and ft <n> from the gdb console, I can see the function lines.  Is there a way to refresh the VS/VGDB debugging windows without restarting?

Thanks, guys!