Why does creator start in different location?

[DaHu_285096]

 I was running debug sessions and noted the debugger started at start of code in main.c

   

Now, for some reason, it starts in "cm3start.c" ??? Did I inadvertantly click some setting instead of the debug btton or is this some automated feature that it decides to start from somewhere else?

[DaHu_285096]

 The debug option "On un" is set to "Main"

[Bob_Marlowe]

Did you turn on any optimizations?

       

Bob

[DaHu_285096]

 Hi Bob,

   

I wern't aware of doing anything ? I was running the degugger to set points, stopping, chaning cod ein main.c and running again in a debug cycle.

   

It was happily jumping to main each time. Now it jumps to the other position and when I click run it jumps to the reset in main. I now have to hit run twice to run the code.

   

Because I don't know how it got to this state, I cannot get it back to normal.

[Bob_Marlowe]

Clean, close, reboot and a new build did not help?

   

Any warnings?

       

Bob

[MiKO_283856 · Accepted solution]

I'm also having this same behavior now, except that the debug session still runs correctly with only one click.

       

Michel.

       

Edit : upgrading to Creator 3.1 seems to have corrected this problem.

[DaHu_285096]

 Clean build and restart have not worked.

   

I applied latest SP2 patch and still does not change the behaviour.

   

Currently downloading and will install early release 3.1 and see if that changes anything.

[DaHu_285096]

 Same here,

   

Version 3.1 Creator fixes the issue. Debug now starts and beginning of Main.c

[DaHu_285096]

 BTW: Is it mandatory to be a cat lover in this forum 🙂 

[DaHu_285096]

 I installed verison 3.1 of creator. Started debugging but as I started writing code, I got assertion errors

   

Expression BeginFileID == EndfileID (when I attempt to #include a header file or write code).

   

I then reverted back to version 3 creator but now the toolchain does not work (the components were all updated in the project when I installed version 3.1).

   

How to I get back the original toolchain ? I did select to archive it when first running the project in version 3.1

   

Seems I have to live with the debugger starting i another module and getting to main on second click of run button.

[Anonymous]

This seems a bug in the cypress decorator interpreter.

Place a newline at end of your code.
https://www.mail-archive.com/llvmbugs@cs.uiuc.edu/msg31225.html//www.mail-archive.com/llvmbugs@cs.uiuc.edu/msg31225.html

Hope they'll fix it soon, this is against misra compliance.
M.