RealView® Debugger User Guide 2.1.1. Syntax of the rvdebug command

2.1.1. Syntax of the rvdebug command

The syntax for starting RealView Debugger at the command-line is as follows:

rvdebug [-b|-cmd][-install=pathname][-user=name][-home[=]pathname] [-aws=pathname|-aws=-][-init[=]connection [-exec[=]image_pathname]] [-inc[=]pathname][-jou[=]pathname][-log[=]pathname][-stdiolog[=]pathname] [-nologo]

where:

-aws

Runs a RealView Debugger session with the specified workspace. This overrides any workspace specification that was stored when the previous session ended.

Use -aws=- to start without a workspace.

-batch

Runs a RealView Debugger session in batch mode, that is without any user interaction.

Use this with -inc to run a script file containing commands.

Can be replaced with -b.

Note

Do not use -batch without -inc. If you do, RealView Debugger runs as a hidden process, and you have to use the Task Manager to terminate the rvdebug process on Windows, or kill the rvdebug process on Sun Solaris or Red Hat Linux.

-cmd

Runs the RealView Debugger in command line mode, where you can use RealView Debugger CLI commands to carry out debugging tasks. This enables you to interact with the debugger without using the RealView Debugger GUI. See the RealView Debugger v3.0 Command Line Reference Guide for detailed information on the RealView Debugger CLI commands.

-exec

Specifies the image to be loaded when RealView Debugger runs. The image specification can also include section details and image arguments, and has the format:

-exec[=] "image[;sections][;arguments]"

where:

image is the image name, and path if required
sections is a comma-separated list of sections
arguments is a space-separated list of arguments
= is optional.

Note

You can optionally use -init to specify a connection when loading an image in this way. If you omit -init, then RealView Debugger can either save a connection in the workspace (see CONNECTION), or display a prompt asking if you want to defer the load until a connection is available.

-home

Specifies a RealView Debugger home directory used for the debugging session. You can optionally include =, for example -home=homedir. If the specified directory does not exist, a new one is created. Where this is not specified, the default directory is used.

Note

This option is only available under Windows. On Sun Solaris and Red Hat Linux platforms, RealView Debugger uses $HOME/rvd for its home directory. This can be overridden by specifying a new home directory using the $RVDEBUG_HOME environment variable (see Setting user-defined environment variables).

See Defining the home directory on Windows for details.

-inc

Runs a specified script file that contains RealView Debugger commands. You can optionally include =.

Use -inc in:

Batch mode in association with the -batch setting, to execute the commands contained in the script file and then exit the debugger.
Command-line mode in association with the -cmd setting, to execute the commands contained in the script file. If the script file does not force RealView Debugger to exit, then the RealView Debugger displays the CLI prompt ready for you to continue debugging.
GUI mode (that is, without -batch and -cmd), to execute the commands contained in the script file during a debugging session. If the script file does not force RealView Debugger to exit, then the RealView Debugger Code window remains open ready for you to continue debugging.

For more details, see Chapter 14 Debugging with Command Scripts.

-init

Specifies the connection to establish when RealView Debugger runs. You can optionally include =, for example -init=connection. This option requires that you specify the connection using the named connection format:

@target_device@Target_Access

For example, @new_arm@localhost for RealView ARMulator^® ISS (RVISS).

-install

Specifies the installation directory where this differs from the default installation. This must point to the following directory:

install_directory\RVD\Core\...\platform

On Windows systems, this is then used to define the location of the default RealView Debugger home directory when the debugger runs for the first time.

This overrides the environment variable RVDEBUG_INSTALL, and must be used if RVDEBUG_INSTALL is not set.

-jou

Runs a RealView Debugger session with the specified journal file open for writing. You can optionally include =, for example -jou=filename. Can be replaced with -j.

See Types of log and journal files for more details about journal files.

-log

Runs a RealView Debugger session with the specified log file open for writing. You can optionally include =, for example -log=filename. Can be replaced with -l.

See Types of log and journal files for more details about log files.

-nologo

Runs a RealView Debugger session without displaying a splash screen.

-stdiolog

Runs a RealView Debugger session with the specified STDIOlog file open for writing. You can optionally include =, for example -stdiolog=filename. Can be replaced with -s.

See Types of log and journal files for more details about log files.

-user

Specifies the user ID in the RealView Debugger home directory used for the debugging session. This argument is available only on Windows platforms. Where this argument is not specified, the default Windows login is used.

See Defining the home directory on Windows for details.

Copyright © 2002-2006 ARM Limited. All rights reserved.	ARM DUI 0153H
Non-Confidential
PDF version