run—Simulator front-end
Contents
Copying
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/copy‐
left/.
GNU Tools 13oct1993 run(1)
Description
Use `runprogram' to execute a binary by interpreting machine instructions on your host computer.
run is the same emulator used by GDB's `targetsim' 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.
Name
run—Simulator front-end
Options
-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 profil‐
ing information was generated.
-pfreq
Generate profile information (for use with gprof). freq is the profiling frequency. Write the
profiling information to a file called gmon.out.
-mmemory
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.
--sysrootfilepath
Prepend filepath to all simulator system calls that pass absolute file paths. Change working di‐
rectory to filepath at program start. Not all simulators support this option; those that don't,
will ignore it.
See Also
`gprof' entry in info; `gdb' entry in info; UsingGDB:AGuidetotheGNUSource-LevelDebugger, Richard
M. Stallman and Roland H. Pesch.
Synopsis
run [-v] [-pfreq] [-mmemory] [--sysrootfilepath] program
