Open and Closed Issues for TASKING Debugger v1.0r1

Open Issues

This is a list of currently open issues that are not marked as closed for the TASKING TASKING Debugger v1.0r1 and older versions. The list may include issues that apply to later releases. See below for the list of closed issues. The list of fixed issues for v1.0r1 is included in the release notes of the product.


ID Summary
DBG-215 Simulator crashes when fast single stepping is used
DBG-221 Language extensions not highlighted in the Eclipse environment
DBG-252 Debugger shows empty heap
DBG-254 Unexpected results for multi-core source level stepping
DBG-257 Errors occur when blink_aurix example is used with the wrong board
DBG-263 Example fssdemo in simulator does not run as expected
DBG-266 Example "whets" cannot be paused or halted in the simulator
DBG-284 Script debugger option "run_to_main" of $download(...) does not work
DBG-285 Application may run past main() upon debugger launch if processor initially running
DBG-287 Expressions view always reverts to the default expression format after single stepping
DBG-288 Debugger stops before PCP error on a PRAM partition check
DBG-290 Debugger Variables view has no feature to show (s)fract type variables
DBG-293 FSS support does not work for TriCore and PCP at the same time
DBG-304 Move to Line feature is always disabled
DBG-306 Resource out of sync error will not go away
DBG-308 Using "Resume at Line" gives "Debug Event Dispatch" error
DBG-329 STM0 timer not stopped when breakpoint is hit or during single stepping
DBG-338 Data breakpoints do not work when MCDS debugging is used

Closed Issues

This is a list of closed issues that will not be fixed. The list of fixed issues for v1.0r1 is included in the release notes of the product.

Won't Fix

ID Summary
DBG-291 Incorrect behavior involving mirrored memory ranges

Table of Contents