Provided by: gdb-msp430_7.2a~mspgcc-20111205-2_amd64
run [-v] [-p freq] [-m memory] [--sysroot filepath] program
Use `run program' to execute a binary by interpreting machine instructions on your host computer. run is the same emulator used by GDB's `target sim' command. You can run it directly by executing run if you just want to see your program execute, and do not need any debugger functionality. You can also use run to generate profiling information for analysis with gprof.
-v Verbose output. Display the name of the program to run before execution; after execution, display the number of instructions executed, the number of machine cycles emulated, the number of pipeline stalls, the real time taken, the emulated execution time taken, and a summary of how much profiling information was generated. -p freq Generate profile information (for use with gprof). freq is the profiling frequency. Write the profiling information to a file called gmon.out. -m memory Set the memory size for the emulated machine to two to the power memory. The default value is 19, emulating a board with 524288 bytes of memory. --sysroot filepath Prepend filepath to all simulator system calls that pass absolute file paths. Change working directory to filepath at program start. Not all simulators support this option; those that don't, will ignore it.
`gprof' entry in info; `gdb' entry in info; Using GDB: A Guide to the GNU Source-Level Debugger, Richard M. Stallman and Roland H. Pesch.
Copyright (c) 1993, 2000 Free Software Foundation, Inc. This document is distributed under the terms of the GNU Free Documentation License, version 1.1. That license is described in the sources for this manual page, but it is not displayed here in order to make this manual more consise. Copies of this license can also be obtained from: http://www.gnu.org/copyleft/.