|
上传最新的AVR Studio 中文HELP。点击此处下载armok0198467.rar
其中有一段文字没有翻译,请大家帮助翻一下(hotpower在吗,请帮忙)。
它是AVR Studio - 调试 - 断点 - 数据断点 一页中的部分内容。
------------------------------------------------------------------------------------------
特别注意事项(Special considerations)
Local variables must always be qualified with the function name. This is also the case if the user wants to add a variable from the function that the program has stopped in.
False hits on data breakpoints on local variables can be caused by reuse of registers. Depending of the level of optimalization, the compiler might try to reuse a register for several variables. Currently, only the IAR compiler in combination with the ICE50 will be able to mask out false hits caused by this. With other compilers, and other platforms such as the simulator or JTAGICE mkII, false hits may be a problem in some cases. In most cases the user can reveal the reason for false hits by examining the code in the disassembly window (or examining a dump of the object file if possible). The 'Custom Scope' settings in the data breakpoint property page can be used to specify a smaller scope for a data breakpoint if it is shared between variables within a function.
The expression parser used for the data breakpoint includes file static functions and variables in the global scope. In cases where several static functions or variables have the same name and are not explicitly qualified with the file name (using the form {<file> [,<function>]} <variable>}, the expression parser will select the first symbol it finds when it scans the symbol table.
The current implementation of the expression evaluator cannot differentiate between overloaded C++ functions. Currently, functions cannot be qualified with their argument list, which is necessary for selecting a specific function overload. The program breakpoint will be bound to an arbitrary instance of the overloaded function.
The data breakpoint implementation in the simulator and the ICE50 can in some cases fail to detect access to a location referenced by a pointer when msb access type is selected. The problem exists when the pointer is stored in X or Z, and ST/LD X/Y with increment is used to de-reference the pointer.
To make sure the debugger breaks, let access type 'Any' be selected.
翻的好的(以我采用为准),奖励50元左右的的电子元件。器件在阿莫的邮购部中选择并提供邮购,费用我出。
请发表在本帖下。 |
|