14.8 Programming advice and noteworthy information

Investigating issues in Python code for an OS awareness extension can sometimes be difficult.

Here are a few recommendations to make debugging easier:
  • Start Eclipse from a console.
    Python print statements go to the Eclipse process standard output/error streams, which are not visible unless Eclipse is started from a console.
    • On Linux, open a new terminal and run:
      <DS-5 installation folder>/bin/eclipse
    • On Windows, open command prompt and run:
      <DS-5 installation folder>\bin\eclipsec
      Note the trailing c in eclipsec.
  • Use the Error Log view.
    Most errors that occur in the debugger are logged in details in the Error Log view. The full stack trace of an error is particularly useful as it often contains references to the location in the source files that generated the error.
  • Turn on verbose error logging in the debugger
    Although most errors are logged in the Error Log view, any error happening in the debugger event processing logic is not. One alternative is to turn on verbose error logging to print the full stack trace of errors in the Console view.
    To turn on verbose error logging, execute the following command early in the debug session:
    log config infoex


    • It is worth understanding that an OS awareness implementation interacts at the deepest level with the debugger, and some errors may cause the debugger to lose control of the target.
    • Also note that semihosting is not available when OS awareness is specified.
Non-ConfidentialPDF file icon PDF versionARM DUI0446W
Copyright © 2010-2015 ARM. All rights reserved.