Thanks for the response. I tried running GDB from the command line and it seems to be taking a long time on the step
~”Reading symbols from <project name>…\n”
where it hangs up for around 20 seconds, same as when I was running it via VisualGDB. After that I could interact with GDB via the command line and it responded quickly.
I have no idea if this is related but there were some warnings while re-building the project that I don’t recall seeing before:
Linking ../VisualGDB/Debug/fwip…
c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-none-eabi/12.2.1/../../../../arm-none-eabi/bin/ld.exe: c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-none-eabi/12.2.1/thumb/v7e-m+fp/hard\libc_nano.a(libc_a-fstatr.o): in function `_fstat_r’:
fstatr.c:(.text._fstat_r+0xe): warning: _fstat is not implemented and will always fail
c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-none-eabi/12.2.1/../../../../arm-none-eabi/bin/ld.exe: warning: ../VisualGDB/Debug/fwip has a LOAD segment with RWX permissions
I’ll see if I can change the ARM toolchain and get a different outcome next.