Wiki

Analog Devices Wiki

English
English
简体中文
简体中文
日本語
日本語
Руccкий
Руccкий

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
resources:tools-software:crosscore:cces:getting-started:debug [18 Jun 2019 21:06] – [Setting Breakpoints] Chad Wentworthresources:tools-software:crosscore:cces:getting-started:debug [18 Jun 2019 21:09] (current) – clarified some sections and added headers Chad Wentworth
Line 51: Line 51:
  
 After you have placed your breakpoints, you can then resume the debug session via the **Run → Resume** pull-down, by striking the **F5** key, or by clicking the green resume arrow in the **Debug** view toolbar. After you have placed your breakpoints, you can then resume the debug session via the **Run → Resume** pull-down, by striking the **F5** key, or by clicking the green resume arrow in the **Debug** view toolbar.
 +
 +=====Viewing Variable Values=====
  
 We can also find the value of a variable in our application. Go to the **Expressions** view, which can be found in **Window → Show View → Expressions**. Click on //Add new expression//, type the variable name in the new expression text box. Hit Enter, and you will see the **Expressions** view populate the **Type** and **Value** columns for the variable, as shown in Figure 4. We can also find the value of a variable in our application. Go to the **Expressions** view, which can be found in **Window → Show View → Expressions**. Click on //Add new expression//, type the variable name in the new expression text box. Hit Enter, and you will see the **Expressions** view populate the **Type** and **Value** columns for the variable, as shown in Figure 4.
Line 59: Line 61:
  
 Note that any value that has changed since the last suspension point will be highlighted in yellow. This is extremely useful if you are trying to debug multiple variables at the same time. Additionally, note that each core has its own set of variables, so the value of an expression can change or become invalid when a different processor is selected. Note that any value that has changed since the last suspension point will be highlighted in yellow. This is extremely useful if you are trying to debug multiple variables at the same time. Additionally, note that each core has its own set of variables, so the value of an expression can change or become invalid when a different processor is selected.
 +
 +=====Other Debugging Views=====
  
 Some other useful views that aid in debugging that can be found under **Window → Show View** include: Some other useful views that aid in debugging that can be found under **Window → Show View** include:
resources/tools-software/crosscore/cces/getting-started/debug.txt · Last modified: 18 Jun 2019 21:09 by Chad Wentworth

Page Tools