when used as Cortex-Debug gdbserver, program cannot stop at breakpoint if there isn't FlashRegion in memory map definition.

the memory map definition in CoreSightTarget is:

return MemoryMap(
                RamRegion(name="Code",          start=0x00000000, length=0x20000000, access='rwx'),
                RamRegion(name="SRAM",          start=0x20000000, length=0x20000000, access='rwx'),

after start debugging in vscode + Cortex-Debug, the program don't stop at entry of main.

but after changing memory map definition to:

return MemoryMap(
                FlashRegion(name="Code",        start=0x00000000, length=0x20000000, blocksize=0x800, access='rwx'),
                RamRegion(name="SRAM",          start=0x20000000, length=0x20000000, access='rwx'),

after start debugging in vscode + Cortex-Debug, the program stop at entry of main.

So is this a problem?

Start with the CoreSightTarget memory map definition and compare the behavior of Code as a RamRegion versus a FlashRegion. Reproduce the session through VS Code and Cortex-Debug, then inspect the GDB-server breakpoint flow; done means determining whether the region classification causes the failure and documenting or correcting the behavior with a regression check.