• State Not Answered
  • Replies 2 replies
  • Subscribers 20 subscribers
  • Views 179 views
  • Users 0 members are here
Options
Related
How was your experience today?

Next execution statement not working in debug mode when using step into button

himanshu mehta

i am new to assembly and its file structure,
i am using stm32f103c6 along with St-link_v2

all i knew is code starts execution from reset handler, there system_init and __main functions are executed
when i am stepping into system init label then next execution statement(yellow arrow) is pointing to instructions in editor window and also into disassembly window
but when there is turn of __main label then, instead of stepping into __main label whole code gets executed like i have pressed run(f5),
when i use breakpoints at the starting of __main's first instruction then, i could see code execution step by step in disassembly window but not in main editor
if anyone has an idea what going on then it will be greatly helpful as
while debugging its more convenient to watch what going on by looking into steps of instruction written in editor
i have attached a video for better reference, first time i have used a breakpoint at __main label and one could see instruction execution in disassembly window,
second time there is no breakpoint then step into behaved like run(F5)

thanks


drive.google.com/.../view

  • 0 Arm Employee Badge

    I don't have access to your video on Google drive, so I can't see what you did. You should consider that the 'Step Into' button has a different functionality, depending on which window has the focus. If it is the disassembly window, then you step in instructions and when a source file (also assembly source file) has the focus, the debugger will perform single steps until it reaches the next C or Assembly source line. Since __main is a library function without source code, µVision will execute the application in single steps until it reaches main() when a source file has the focus. This may take some time depending on your application because __main needs to initialize variables, heap etc. 

    So you should first click into the disassembly window before you perform single steps (Step Into) in order to single step through assembly instructions.

  • 0 in reply to Hans Schneebauer

    sorry sir for my mistake
    https://drive.google.com/file/d/1QvhnhwXPAX_J5vOoRiktthA1TcHj13ML/view?usp=sharing
    i think that should work
    I am trying to learn assembly for arm and i can see next execution statement(yellow arrow) on disassembly window but not in editor window while in debug mode
    its not a big deal, but if i will start writing complex code then at that time it will be lot helpful if i could see my instructions executing in editor instead in disassembly window
    again thankyou for your time