Hi
When I try to 'Step Into' a constructor during debugging the SES does always show the 'Disassembly' panel instead of jumping to the actual c++ code file.
(This is not a new problem in SES v3.12. In SES v3.10i it is the same.)
My work around is to navigate manually to the constructor and set a break point.
Is there a setting to disable that behaviour?
Regards
Anton
dev machine: Windows 10 64bit, SES v3.12
target mcu: NXP(freescale) MKL27Z128... & KM66FN2...
When I try to 'Step Into' a constructor during debugging the SES does always show the 'Disassembly' panel instead of jumping to the actual c++ code file.
(This is not a new problem in SES v3.12. In SES v3.10i it is the same.)
My work around is to navigate manually to the constructor and set a break point.
Is there a setting to disable that behaviour?
Regards
Anton
dev machine: Windows 10 64bit, SES v3.12
target mcu: NXP(freescale) MKL27Z128... & KM66FN2...