Specifications

Known Issues
blab-srn-005Pa
© CSR plc 2006
This material is subject to CSR’s non-disclosure agreement.
Page 17 of 48
_äìÉi~Ä»=îPKQ= Software Release Note
The following items are known problems with xIDE.
ID Severity Description
M-391 Cosmetic
After an application panic, it's still possible to click step and run in xIDE but they return
error messages.
M-406 Minor
Stepping over MessageLoop will cause xIDE to stop responding until a message is
received.
M-452 Minor xIDE has excessive PC CPU usage while polling a running VM application.
M-455 Minor xIDE takes a long time to load debug information for large VM projects.
M-467 Minor
Stopping xIDE while firmware is being downloaded leaves a stray
BlueFlashCmd.exe process running.
M-469 Major Stepping over functions in Kalimba DSP code in xIDE incorrectly steps into the function.
M-475 Minor
xIDE tracks breakpoints by source line, which means inserting lines in front of the
breakpoint can cause it to move without warning.
M-563 Minor
If auto-indent is enabled then xIDE can incorrectly indent lines when
Undo is used.
M-582 Cosmetic
xIDE sometimes starts with a window partially off the screen; a workaround is to right-
click on xIDE in the task bar and select Move, bringing the window back on screen using
the cursor keys.
M-607 Minor
If local and global variables have the same name, then xIDE will only display one of
them while debugging a VM application.
M-678 Minor
Pointers to opaque types (such as GAVDP) in a VM application sometimes fail to
display correctly in xIDE, even when the type has later been fully defined elsewhere in
the source file.
M-704 Minor
The Stop-Build button produces strange results if pressed during start-up of a Kalimba
project.
M-744 Minor
It is possible for xIDE to open two different buffers onto the same file causing confusion
when changes are made in one of the buffers. (Provoking this requires typing in path
names rather than selecting them from the lists in the file dialogs.)
M-745 Minor
Using F4 in xIDE to go to the next error does not restart from the top of the list of errors
after rebuilding the application.
M-754 Minor
Single stepping through single instruction do loops performs three instructions on each
step.
M-761 Minor
The Kalimba register window groups the registers by type, these groups can be
expanded and collapsed by the user, however, after each run xIDE resets the window
and collapses each group.
M-769 Minor If xIDE is closed while it's switching to debug mode, it crashes with a memory error.
M772 Minor
Batch build builds the active configuration several times, rather than building all the
different configurations.
M-780 Minor
xIDE will fail with a memory exception if operations are performed on a project in a
workspace after the project has been removed (e.g. deleted).
M-815 Minor
Pressing F4 in xIDE to go to the next error can be confused by errors which actually
occur in included files.
M-821 Minor Removing all projects from a workspace crashes xIDE.
M-829 Minor
When debugging a multi-project workspace in xIDE, the project selector in the debug
toolbar can activate the wrong project or show the wrong project as being active.
Selecting and viewing the active project using the navigator pane is an effective
workaround.
M-837 Major
If vm memory or register widgets are opened after a panic, they display all zeros. To
work around this problem, click show next statement on the debug menu after opening
the widgets.
M-842 Minor
Search and replace can take several minutes to complete for a few thousand
replacements.