This is a list of currently open issues for the TASKING Embedded Debugger v1.0r3.
The list may include issues found in later releases, whether such issues also appear in this release has not always been verified yet. See below for the list of closed issues. The list of fixed issues for v1.0r3 is included in the release notes of the product.
ID | Summary | Inspector detector |
DBG-215 |
Debugger crashes when fast single stepping is used |
Not planned |
DBG-252 |
Debugger shows empty heap |
Not planned |
DBG-254 |
Unexpected results for multi-core source level stepping |
Not planned |
DBG-257 |
Errors occur when blink_aurix example is used with the wrong board |
Not planned |
DBG-263 |
Example fssdemo in simulator does not run as expected |
Not planned |
DBG-266 |
Example "whets" cannot be paused or halted in the simulator |
Not planned |
DBG-284 |
Script debugger option "run_to_main" of $download(...) does not work |
Not planned |
DBG-285 |
Application may run past main() upon debugger launch if processor initially running |
Not planned |
DBG-287 |
Expressions view always reverts to the default expression format after single stepping |
Not planned |
DBG-288 |
Debugger stops before PCP error on a PRAM partition check |
Not planned |
DBG-290 |
Debugger Variables view has no feature to show (s)fract type variables |
Not planned |
DBG-293 |
FSS support does not work for TriCore and PCP at the same time |
Not planned |
DBG-306 |
Resource out of sync error will not go away |
Not planned |
DBG-338 |
Data breakpoints do not work when MCDS debugging is used |
Not planned |
DBG-390 |
Adding a TASKING Breakpoint not possible |
Not planned |
DBG-397 |
A project created with MIL linking cannot be debugged |
Not planned |
DBG-419 |
Problem related to access of non-readable SFR memory ranges |
Not planned |
DBG-471 |
Multi-core debugging not compliant to DAS driver version 7.2.0 |
Not planned |
This is a list of issues that have been closed with a resolution other than fixed. This list contains issues that will not be fixed, issues that appeared to be not a problem and/or issues that could not be reproduced. The list of fixed issues for v1.0r3 is not shown here, it is included in the release notes of the product.