Tim, is GDB a lower priority or unsupported?
I understand, as a small organization, support resources being stretched and responses will not be immediate. But I am seeing threads just end abruptly on this topic and in another thread your statement...
Visual Micro wrote on Sep 8
th, 2018 at 12:12pm:
Hi,
There has been a lot of changes in the IDE's in relation to GDB. It will be re-done over the coming months.
In the meantime I am sorry that there is no support time available to help people with GDB .
I suggest looking for an alternative or use the serial debugger
Thanks
The VM software-based debugging is not cutting it for our needs as we support our customers using our libraries. We have invested quite a few hours over the last several weeks getting openOCD functional with our Segger hardware and the target boards. We have used the VM burn bootloader functionality (via the J-Link) and the last hurdle is simply why VM won't recognize the settings as spelled out in your documentation to enable vMicro>>Debugging>>Microsoft GDB Debugger.
#board.txt or platform.txt
debug.tool=gdb
If there is no support for GDB with Visual Micro, I regrettably will have to migrate off of Visual Micro to another toolset, most likely Platform IO. Given that we have been using VM for two years and built processes around Visual Micro this is not something I am looking forward to but I can't wait months.
Sorry to be so direct,
Greg