I've had some trouble using arm-none-eabi-gdb, however, fortunately, I've just fixed it. But even when changing to the arm tool, the same error occurs. The content around Reset_Handler was added to the question, it's better formatted there than here, in the comment. I also included the dump I generated with arm-none-eabi-objdump of the elf generated by the compilation process. The content of the dumped memory is different from the objdump generated in my dev environment. I don't have any idea what's causing the difference between them.

I use stlink server: "st-util build/stepper-driver.bin /dev/stm32f4". The debug hardware is already present in the Nucleo board that I've been working with.

Do you have any idea about the first problem I described? It's been a long time I've been stuck at it, and I don't have any idea what's causing it.

I still don't know what's happening, but I noticed that the function address pointed by the dump code is different from what is shown by the gdb-multiarch. In the dump, the address of my function "ConfigureWatchdogs" is 0x08000d30. However, when I set the breakpoint "b ConfigureWatchdogs", gdb returns 0x08000d34.

It worked! Thank you very much!