This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Avoid breakpoint during debugging on first line of main

Short and simple question: Is there a way to NOT break on the start of main when I debug my app using SES? 

Parents
  • Do Target > Download

    Then, when you want to debug, do Target > Attach debugger

  • Hi awneil,

    while this is certainly right, it might have missed the chance to describe my intent more clearly. Its not that I want to attach at an arbitrary point in time - the debugger should honor the set breakpoints, just not the invisible one at the beginning of main().

    Example: I want to debug some func when setting up the BLE stack and print a lot of debug infos along the way. Now every time I start debugging, I will need to switch to SES, continue at the initial breakpoint, check back in the console log and then back to SES to where it is. I'd rather start the debug, switch immediately to the console and read and then back to SES. A little bit a constructed example but it illustrates my point. Is this possible?

Reply
  • Hi awneil,

    while this is certainly right, it might have missed the chance to describe my intent more clearly. Its not that I want to attach at an arbitrary point in time - the debugger should honor the set breakpoints, just not the invisible one at the beginning of main().

    Example: I want to debug some func when setting up the BLE stack and print a lot of debug infos along the way. Now every time I start debugging, I will need to switch to SES, continue at the initial breakpoint, check back in the console log and then back to SES to where it is. I'd rather start the debug, switch immediately to the console and read and then back to SES. A little bit a constructed example but it illustrates my point. Is this possible?

Children
No Data
Related