Debugging not working

[ninjasource]

Hi,

Thank you for your very comprehensive wiki:
https://medium.com/coinmonks/coding-the-stm32-blue-pill-with-rust-and-visual-studio-code-b21615d8a20

It is great to have all the VS Code tasks set up like that. I can build successfully (after applying the outstanding pull request) and connect using the gdb task you created. However, when I press "Start Debugging" I get the following message "target halted due to debug-request, current mode: Thread" in the terminal but no breakpoint is hit. I expected a break just after the main function entry point. Additionally, clicking "Start without Debug" does not appear to flash the STM32 device as you would expect. In fact, nothing happens. Any ideas would be greatly appreciated!
I am using the same STM32F103 board from your wiki.

Here is some of the output:

---

Terminal Output

---

...some output before the line below...
Info : accepting 'gdb' connection on tcp/3333
target halted due to debug-request, current mode: Thread
xPSR: 0xa1000000 pc: 0x1ffff3b6 msp: 0x200000c4
Info : device id = 0x20036410
Info : flash size = 64kbytes
semihosting is enabled
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x1ffff020 msp: 0x200001fc, semihosting

---

Debug Console Output:

---

The target architecture is assumed to be arm
warning: No executable has been specified and target does not support
determining executable automatically. Try using the "file" command.

0x1ffff3b6 in ?? ()
Not implemented stop reason (assuming exception): undefined
semihosting is enabled
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x1ffff020 msp: 0x200001fc, semihosting
Function "stm32_blue_pill_rust::main" not defined.

[mInzamamMalik]

+1

[laplacedoge]

It works for me after I connect it to the 5V power.