AnsweredAssumed Answered

Breakpoint in unused function is moved to another function

Question asked by SCOTT MILLER on May 27, 2018
Latest reply on Jun 4, 2018 by LPCX presso support

Running MCUX 10.2.0 - and this time it's a completely fresh, unmodified install with no PEx or non-standard toolchain.


I'm debugging my USB descriptor handling code and set a breakpoint in USB_Desc_Valid_Configation().  (You can tell it's from a Freescale example because 'configuration' is misspelled.  Along with 'composite', 'function', 'is', 'successful', 'received', 'supported', 'increase', 'interface'...)  I forgot, however, that the function isn't actually referenced.  Nor is the next function.


The result is that the breakpoint invisibly moves to an entirely different function further down.  I understand that picking the next line that actually produces any code is typical, but shouldn't it be confined to a single function?  And I seem to remember that CodeWarrior would visibly move the breakpoint marker to its actual location.