Known Problems

• IDE-6264
  

  If a workspace with floating windows is closed, one or more of those floating windows might be docked when the workspace is opened again.

• IDE-5527
  

  The time to switch between IDE mode and Debug mode might be negatively affected by the number of open Debug windows.

• IDE-7672
  

  The Go to call command on the context menu in the Call Graph window might jump to an incorrect position when the selected function is in a header file.

• IDE-7645
  

  The source browser cannot handle nested C macros.

• IDE-7593
  

  When using the Chinese Simplified (GB2312) character encoding, the text editor might display incorrect character positioning—especially on long lines—when running on high-DPI displays with scaling enabled. For example, this can occur on a 4K monitor with 150% display scaling.

• IDE-7279
  

  The editor might in rare cases perform editing operations at another position than where the cursor is.

• IDE-7275
  

  The editor shortcut key for the Find dialog box (Ctrl + F) might in some rare cases stop working.

• IDE-7141
  

  When running IAR Embedded Workbench on a system with a non-English locale, buttons like OK and Cancel might be in the locale language in some dialog boxes, and in English in other dialog boxes.

• IDE-6905
  

  Not having the environment variable HOME set on Linux might lead to problems, including termination of the process.

• IDE-6679
  

  Switching from building an executable file to building a library file can leave old output entries displayed in the Workspace window,

• IDE-6478
  

  When using the device selector button to select a target device on the Project>Options>General Options>Target options page, clicking the down arrow at the end of the list of devices to scroll downward, might result in multiple devices being selected.

• IDE-6223
  

  The parsing rules in the Watch window might fail when trying to show ambiguous grammar constructs in C++ source code.

• IDE-6083
  

  Using the Tab key when the option Indent with spaces is selected in the Editor category of the IDE Options dialog box might calculate the indentation incorrectly for Japanese characters.

• IDE-6056
  

  Code folding (expanding/collapsing portions of the code) in the editor might perform collapsing incorrectly for complicated constructs.

• IDE-6018
  

  Use of the keyword asm might be flagged as incorrect by the editor's syntax feedback feature.

• IDE-5882
  

  If you use Alt-drag or Alt+shift+Down Arrow (or Up Arrow) to add a tab character to multiple lines in an editor window, the insertion point can under some circumstances end up on the left side of the inserted tab character(s).

• IDE-5814
  

  The editor syntax feedback might make incorrect assumptions about the size of fundamental types, and give misleading warnings.

• IDE-5805
  

  For some fonts and font sizes, in combination with some screen resolutions, the insertion point might appear to be one character off in the editor window.

• IDE-5802
  

  On rare occasions, the internal information on how the IDE windows are docked can become corrupted. This triggers crashes when a debug session is ended. To solve this, delete the *.wsdt file in the settings folder in the project directory.

• IDE-5780
  

  The syntax feedback in the editor might produce multiple warnings when a type specifier is missing, because it always assumes that the missing type is int.

• IDE-5669
  

  The source browser might have issues with projects having paths containing non-ASCII characters.

• IDE-5279
  

  When the view of the Registers window is narrowed in the horizontal direction, the drop-down arrow for choosing a register group might be hidden. In that case, use the horizontal scroll bar to view the register group.

• IDE-5229
  

  The source browser might fail to parse files and will display the error message:
  Paths are too long. Please move the browse info folder.

• IDE-5180
  

  Breakpoints are not always tracked correctly when inserting source code before the breakpoint.

• IDE-5162
  

  The multi-file compilation option might not be included when creating a new configuration.

• IDE-5160
  

  Register format in the Registers window is not saved across debug sessions when the selected format is hexadecimal.

• IDE-5058
  

  The IAR Embedded Workbench IDE might have problems showing text properly on high resolution displays.

  
  See also: IDE-4587 IDE-4579

• IDE-4750
  

  In an initial multicore debugging session, the configuration names might be wrong.

• IDE-4704
  

  On a multiple monitor setup, if the IAR Embedded Workbench has been opened on a secondary screen and then the user decides to only use the primary screen, the IAR Embedded Workbench might become hidden because it still uses the screen coordinates of the now defunct secondary monitor.

• IDE-4692
  

  Due to simplified parsing rules, the Watch window might now show variables which have the same identifier as a type name.

• IDE-4688
  

  The Source Browser window can confuse the Shift-JIS encoding with UTF-8.

• IDE-4638
  

  Moving the boundary between docked windows might leave an extra gap below the horizontal scroll bar in the editor window.

• IDE-4621
  

  The checks 17.1 , 17.2, and 17.3 have check boxes in the Options page for MISRA 2004. This might mislead the user to think that 17.1 , 17.2, and 17.3 are checked by the tool, but they are not checked by the tool as noted in the documentation.

• IDE-4605
  

  If a file whose name is just too long to fit at the end of the row of tabs in the editor window is opened, the file will not be visible in the row of tabs.

• IDE-4593
  

  When iarbuild.exe loads a project generated with an older version of IAR Embedded Workbench, the project file is not updated to the new version.

• IDE-4589
  

  Editing or in other ways changing the project file while the IAR Embedded Workbench is active is not supported.

• IDE-4587
  

  The IAR Embedded Workbench might have issues with high DPI displays.

  
  See also: IDE-5058

• IDE-4579
  

  The Embedded Workbench IDE can have problems showing graphical elements properly if the screen resolution is changed.

  
  See also: IDE-5058

• IDE-4561
  

  The IAR Embedded Workbench might have issues with high DPI displays.

• IDE-4531
  

  When undocking windows from the IAR Embedded Workbench and then docking them together, still outside the IAR Embedded Workbench main window, the undocked windows will not show up when restarting the IAR Embedded Workbench.

• IDE-4526
  

  The shortcut key for the command Project>C-STAT Static Analysis>Analyze File(s)  (Ctrl+Shift+F7) might not work when the editor window is in focus.

• IDE-4516
  

  Closing an undocked window during a debug session will make it reappear in the next debug session. (As opposed to a docked window; a docked window getting closed during a debug session will not reappear in the next debug session).

• IDE-4488
  

  Using casts in the Watch window might fail because of ambiguous grammar. A workaround could be to provide some context, for example, (struct Derived *) instead of just (Derived *).

• IDE-4443
  

  When the C-SPY debugger is started, a message Flash download error: Failed to open file xxx.sim can be displayed, caused by the .sim file being locked.

• IDE-4442
  

  Font and Color settings are not inherited from older to newer versions of the Embedded Workbench IDE.

• IDE-4438
  

  Beginning with IAR Embedded Workbench shared components version 8.1, build actions (specified in the Project>Options>Build Actions dialog box) will execute as 'attached' processes, meaning that they no longer can open a separate window. To see the version number of the IAR Embedded Workbench shared components, choose Help>About>Product Info.

• IDE-4186
  

  The TI-RTOS plugin might open a large number of windows when the C-SPY Debugger is started.

• IDE-4162
  

  Having two editor windows docked side by side on two monitors can cause problems with the window scrollbars.

• IDE-4066
  

  Redrawing the IDE status bar on the screen can fail, especially when the display scaling is changed.

• IDE-4059
  

  The column labels in the Data Sample window are not updated when you switch variables in the Data Sample Setup window.

• IDE-3991
  

  Command line options, for example include paths, that end with two or more backslashes might give error message "[Su009]: Missing closing quote in command file".

• IDE-3959
  

  Because of a conflict with the Windows operating system, some IAR Embedded Workbench shortcut keys that contain the Alt key no longer work.

• EW25524 / IDE-2671
  

  When a breakpoint set at "memset();" triggered, the execution might halt at "__aeabi_memset(_D, _N, _C);" in DLib_Product_string.h.

• EW24226 / IDE-2513
  

  In some rare cases after performing a "Rebuild All" command, executing a "Download and Debug" command might not start the debug session. Executing a "Clean" command solves this problem.

• EW25237 / IDE-2479
  

  Pressing "Debug without Downloading" very rapidly creates a crash.

• EW25115 / IDE-2354
  

  After stepping over a statement that changes the value of the current stack pointer (for example by way of changing which SP that is the current SP) the execution might not stop as expected.

• EW24690 / IDE-2181
  

  If the embOS plugin is enabled, the contents of Locals window might fail to refresh when the execution stops.

• EW24090 / IDE-1871
  

  If you enable Code Coverage in the Disassembly window, it might be incomplete unless you also enable the Function Profiler and choose "Source Trace (flat)" from the context menu in the Function Profiler window.

• EW23847 / IDE-1639
  

  If a collapsed group of files in the Workspace window contains a file that will be rebuilt next time the project is built, the red star icon might not be shown in the build status column. However, if the file group is expanded, the icon is shown correctly.

• EW23821 / IDE-1611
  

  Files that are not members of a project can be checked out but not checked in again if you are using the IDE SCC integration.

• IDE-1355
  

  Disabling "Function Profiler" do not disable "Power Sampling".

• EW23347 / IDE-1347
  

  If you close the Disassembly window while it is the active window, it will be reopened every time execution stops.

  Workaround:
  Click in the editor window to make it active before you close the Disassembly window. Now then the Disassembly window will only reopen when the execution stops at a location that does not have any corresponding source code.

Trademarks

IAR Systems, IAR Embedded Workbench, C-SPY, visualSTATE, The Code to Success, IAR KickStart Kit, I-jet, IAR, and the logotype of IAR Systems are trademarks or registered trademarks owned by IAR Systems AB.

Microsoft and Windows are registered trademarks of Microsoft Corporation. Adobe and Acrobat Reader are registered trademarks of Adobe Systems Incorporated. CodeWright is a registered trademark of Starbase Corporation. All other product names are trademarks or registered trademarks of their respective owners.

Copyright © 1996-2025 IAR Systems AB.