Confusing behavior of asm with memory

[MLalu.1]

I try to better understand assembly so I use STcubeIDE debugger to see how my C code is translate in asm langage. But I dont understand a thing. In the asm code I see that it regulary "jump" on memory addresses where there is nothing (only FFFFFFFF) or it is going to search or write data in non accessible memory (such as "0x2020202c" or "0x20202028"). The aim of my code is simply to use the button on my NUCLEO-64 board to blink the embedded green led. I was surprised to see that my asm code use the "non accessible memory adresses" instead of the GPIO registers adresses. Could someone help me to understand this behavior ?

[Tesla DeLorean]

Would seem some information is being misinterpreted somewhere.​

[Ozone]

I would say, either use a tool like objdump to create asm files, or step through with the debugger in instruction-step-mode.

You might misinterpret data oe empty sections.

[Tesla DeLorean]

Yeah, I'd start with a static analysis of the sources vs linker output disassembly, and then assess if the debugger or user is reporting cogent information. ​

[MLalu.1]

ok ... thank you ! I'm going to try with the debugger in instruction-step-mode to see where is my problem.