Anonymous
Not applicable
Aug 29, 2016
01:42 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aug 29, 2016
01:42 PM
All of a sudden, I can not set regular breakpoints. Instead WICED is setting these "hit points". I see the little dot next to the instruction. When the program encounters one, it reports that it hit that point in the console but it doesn't stop so that I can look around or single step. How do I get WICED back to setting traditional breakpoints the way it used to work?
Solved! Go to Solution.
Labels
- Labels:
-
Debug
1 Solution
Anonymous
Not applicable
Aug 30, 2016
06:18 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aug 30, 2016
06:18 AM
Figured it out.
Right click the breakpoint symbol to the left of the instruction.
Select breakpoint type.
Choose C/C++ breakpoint as opposed to Dynamic printf.
2 Replies
Anonymous
Not applicable
Aug 30, 2016
06:18 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aug 30, 2016
06:18 AM
Figured it out.
Right click the breakpoint symbol to the left of the instruction.
Select breakpoint type.
Choose C/C++ breakpoint as opposed to Dynamic printf.
Aug 30, 2016
06:41 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aug 30, 2016
06:41 AM