Breakpoint triggers on bad line number
Sure I am using debug configuration and compiling with these settings:
-mcpu=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -std=c++11 -DSTM32F446RETx -DNUCLEO_F446RE -DSTM32F4 -DSTM32 -DDEBUG -DUSE_HAL_DRIVER -DSTM32F446xx -I"C:\Users\michp\git\flyhero\nucleo-f446re_hal_lib" -I"C:\Users\michp\git\flyhero\IMU (in development)/inc" -I"C:\Users\michp\git\flyhero\nucleo-f446re_hal_lib\CMSIS\core" -I"C:\Users\michp\git\flyhero\The_Eye\inc" -I"C:\Users\michp\git\flyhero\LEDs\inc" -I"C:\Users\michp\git\flyhero\nucleo-f446re_hal_lib\CMSIS\device" -I"C:\Users\michp\git\flyhero\nucleo-f446re_hal_lib\HAL_Driver\Inc\Legacy" -I"C:\Users\michp\git\flyhero\nucleo-f446re_hal_lib\HAL_Driver\Inc" -I"C:\Users\michp\git\flyhero\nucleo-f446re_hal_lib\Utilities\STM32F4xx-Nucleo" -O0 -g3 -Wall -fmessage-length=0 -ffunction-sections -c -fno-exceptions -fno-rtti