Executing an Application for Debugging

The way in which you execute an application depends on whether you are performing standard application debugging or analyzing a process dump.

Executing for Standard Application Debugging

If you are performing standard application debugging, the application can be executed in three ways:

• Select Run from the Run menu.

• Click the Run button on the toolbar.

  ---

  Note -

  When GDB is busy (during the execution of a program, for example) the Run button is replaced by a Stop button. Use this button to stop the application.

  ---

• Select View -> Console and use the run command in the View -> Console window.

Troubleshooting Application Execution

If nothing happens when you attempt to execute your application in Insight, perform the following checks:

• Open the Console window and type run.

• If the following message is displayed:

  Warning: executable path does not match the path translation.
  Unable to create remote process, File not found (maybe / has changed). 

  refer to "Loading and Executing the Application" for assistance in solving the problem.

• If you consistently have the same problem, check whether your program links to one or more dynamic libraries. If your program does link to dyamic libraries, you must add the environment variable LD_LIBRARY_PATH, with a value set to the path where the libraries are located.

  You can add the library path environment variable using the ChorusOS Environment Variables window (see "Displaying ChorusOS Environment Variables" for more information), or using the Console window. To add the variable using the Console window, type:

  (chgdb) rdbsetenv LD_LIBRARY_PATH=/bin/examples:/bin/lib PATH=/bin:/sbin HOST= TZ=GMT0 LD_LIBRARY_PATH=/bin/examples:/bin/lib (chgdb)

  where LD_LIBRARY_PATH is the path to the libraries.

Attaching to a Process Dump

Before performing a process dump analysis, select the process dump you want to analyze. Use the ChorusOS Processes window to attach to the process dump. See "Displaying ChorusOS Processes" for more information.

Alternatively, you can use the command-line interface in the Console window.