
High-performance Embedded Workshop V.4.09 Release Note
R20UT0373EJ0100 Rev.1.00 Page 10 of 41
Feb 01, 2011
1.13.5 Stack Trace window
Inline functions that have been expanded as intended are not displayed in the history of function calls.
1.13.6 Reference of variables
(1) Local variables in inline functions
While the PC is pointing to an address in an inline function, you cannot use the windows or functions given
below to reference the parameters of functions or the values of local variables defined in functions.
(2) Local variables after optimization
Depending on the generated object code, the windows and functions given below do not correctly show the
values of local variables in a C source file that is compiled with the optimization option enabled.
Check the generated object code in the [Disassembly] window.
(3) Memory caching
With memory caching enabled, the windows and functions given below may not display the correct values of
variables while a program using little endian is being debugged. For example, the 4-byte variable at address
0x2002 in the following code will not be displayed correctly.
#pragma address data=0x2002
long data;
To prevent this problem, use the CACHE command to disable caching.
For notes on the CACHE command, refer to section 1.17.1, CACHE command.
cache off
• The Stack Trace window
• The Locals window
• The Watch window
• Tooltip Watch function
• Instant Watch function
1.13.7 Watch window
(1) Expanding variables
When a watch item is located outside the scope in debugging of a program, the item is automatically
collapsed if it has been expanded.
The realtime update setting on the first child item applies to the entire watch item.
(2) Automatic update of variables
When a variable has been cast and then added to the Watch window, automatic update of the variable is not
possible.
Comentarios a estos manuales