Open and Closed Issues for TASKING Embedded Debugger v1.0r2Log in
This is a list of currently open issues for the TASKING Embedded Debugger v1.0r2.
The list may include issues found in later releases, whether such issues also appear in this release has not been verified. See below for the list of closed issues. The list of fixed issues for v1.0r2 is included in the release notes of the product.
|| Debugger crashes when fast single stepping is used
|| Debugger shows empty heap
|| Unexpected results for multi-core source level stepping
|| Errors occur when blink_aurix example is used with the wrong board
|| Example fssdemo in simulator does not run as expected
|| Example "whets" cannot be paused or halted in the simulator
|| Script debugger option "run_to_main" of $download(...) does not work
|| Application may run past main() upon debugger launch if processor initially running
|| Expressions view always reverts to the default expression format after single stepping
|| Debugger stops before PCP error on a PRAM partition check
|| Debugger Variables view has no feature to show (s)fract type variables
|| FSS support does not work for TriCore and PCP at the same time
|| Resource out of sync error will not go away
|| Data breakpoints do not work when MCDS debugging is used
|| Debugger error: Loading failed : Target is not responding (timed out)
|| TriCore Example project cannot be imported
|| Viewing local variables (in a C function) sometimes results in message 'no storage assigned'
|| Prevent the Debugger from reading SFR registers when this has a hardware side-effect
|| Adding a TASKING Breakpoint not possible
Improvements and/or New Features
|| Host memory shortage when using large/complex elf files
|| Support non-blocking read in File System Simulation (FSS)
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.0r2 is not shown here, it is included in the release notes of the product.
|| Incorrect behavior involving mirrored memory ranges