Open and Closed Issues for TASKING Embedded Debugger v1.0r1Log in

Open Issues

This is a list of currently open issues for the TASKING Embedded Debugger v1.0r1. 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.0r1 is included in the release notes of the product.


DBG-215 Debugger 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
DBG-354 Debugger error: Loading failed : Target is not responding (timed out)
DBG-363 TriCore Example project cannot be imported
DBG-370 Viewing local variables (in a C function) sometimes results in message 'no storage assigned'
DBG-371 Prevent the Debugger from reading SFR registers when this has a hardware side-effect
DBG-390 Adding a TASKING Breakpoint not possible
DBG-397 A project created with MIL linking cannot be debugged
DBG-419 Problem related to access of non-readable SFR memory ranges
DBG-471 Multi-core debugging not compliant to DAS driver version 7.2.0

Improvements and/or New Features

DBG-301 Support for TC21x (hardware) debugging
DBG-303 Support multiple DAS clock setting configurations
DBG-316 Support for TC39x (hardware) debugging
DBG-317 Host memory shortage when using large/complex elf files
DBG-330 Improve debugger launch preparation time and download time of larger applications
DBG-360 Support non-blocking read in File System Simulation (FSS)

Closed Issues

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.0r1 is not shown here, it is included in the release notes of the product.

Won't Fix

DBG-291 Incorrect behavior involving mirrored memory ranges

Table of ContentsBack