Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

avr-run(1) [debian man page]

run(1)								     GNU Tools								    run(1)

NAME
run--Simulator front-end SYNOPSIS
run [-v] [-p freq] [-m memory] [--sysroot filepath] program DESCRIPTION
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. OPTIONS
-v Verbose output. Display the name of the program to run before execution; after execution, display the number of instructions exe- cuted, 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. SEE ALSO
`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. COPYING
Copyright (c) 1993, 2000, 2012 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/. GNU Tools 13oct1993 run(1)

Check Out this Related Man Page

GCORE(1)						       GNU Development Tools							  GCORE(1)

NAME
gcore - Generate a core file of a running program SYNOPSIS
gcore [-o filename] pid DESCRIPTION
Generate a core dump of a running program with process ID pid. Produced file is equivalent to a kernel produced core file as if the process crashed (and if "ulimit -c" were used to set up an appropriate core dump limit). Unlike after a crash, after gcore the program remains running without any change. OPTIONS
-o filename The optional argument filename specifies the file name where to put the core dump. If not specified, the file name defaults to core.pid, where pid is the running program process ID. SEE ALSO
The full documentation for GDB is maintained as a Texinfo manual. If the "info" and "gdb" programs and GDB's Texinfo documentation are properly installed at your site, the command info gdb should give you access to the complete manual. Using GDB: A Guide to the GNU Source-Level Debugger, Richard M. Stallman and Roland H. Pesch, July 1991. COPYRIGHT
Copyright (c) 1988-2013 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with the Invariant Sections being "Free Software" and "Free Software Needs Free Documentation", with the Front-Cover Texts being "A GNU Manual," and with the Back-Cover Texts as in (a) below. (a) The FSF's Back-Cover Text is: "You are free to copy and modify this GNU Manual. Buying copies from GNU Press supports the FSF in developing GNU and promoting software freedom." gdb-Red Hat Enterprise Linux 7.6.1-51.el7 2014-06-10 GCORE(1)
Man Page