Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ dde(1) — HP-UX ANSI C A.10.11

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

adb(1)

cc(1)

CC(1)

f77(1)

ld(1)

pc(1)

multibyte(3C)

shl_load(3X)

system(3S)

a.out(4)

core(4)

user(4)

lang(5)

signal(5)

dde(1)

NAME

dde − invoke HP/DDE debugger

SYNOPSIS

dde [−do "cmd_list"] [−ui ui_type] [X_options] [−dctimeout msec]
    [ [−wd pathname]
      [−input pathname]
      [−output pathname [−ao]]
      [−errors pathname [−ae]]
      [−setenv env_var=string[,env_var=string]...]
      object_program_pathname [--] [object_program_arguments]
    | −attach process_id [object_program_pathname]
    | core_file object_program_pathname ]

DESCRIPTION

The dde command invokes the HP Distributed Debugging Environment, a high-level debugger for HP systems. For complete information about this debugger and its commands, consult the HP/DDE Debugger User’s Guide and the debugger’s extensive, hypertext-based online help system, which contains a complete command reference as well as task information. You can invoke the online help from the menu bar of the debugger’s Transcript Display window or from the HP VUE front panel Help Manager. 

OPTIONS

−do "cmd_list" Execute cmd_list (a list of debugger commands) before executing any startup files or invoking the target program.  Any shell quoting method may be used for cmd_list; double quotes are not required. 

−ui ui_type Use ui_type user interface.  The default ui_type, motif, invokes the OSF/Motif user interface. You may also specify line, for the line-mode user interface. 

X_options Execute any standard X command line options (for example, −background, −foreground, −display, −xrm, −synchronous, and −reverse).  See X(1) or The X Window System User’s Guide, O’Reilly & Associates, Inc. 

−dctimeout msec Set the mouse double-click timeout interval to msec milliseconds.  By default, the second click must occur within 400 milliseconds (0.4 seconds) of the first click.  You can also set this value in your X resources; see the HP/DDE Debugger User’s Guide for details.  This option applies only to the OSF/Motif user interface. 

−wd pathname Set the working directory of the target program to pathname.  Other relative path name arguments to the dde command are interpreted relative to this directory. 

−input pathname Read the target program’s standard input from pathname. 

−output pathname [−ao]
Redirect the target program’s standard output to pathname.  With -ao, append the target program’s standard output to pathname. 

−errors pathname [−ae]
Redirect the target program’s error output to pathname.  With -ae, append the target program’s error output to pathname.  To redirect error output and standard output to the same file, use the same path name with both −errors and −output. 

−setenv env_var=string[,env_var=string]... 
Set the target program environment variable env_var to the value string.  The string env_var contains the shell environment variable you wish to establish in the target program process.  The string value contains the text to assign to the environment variable.  Spaces are not allowed on either side of the equal sign (=); if you set more than one environment variable, spaces are not allowed on either side of the comma. 

object_program_pathname [--] [object_program_arguments]
Invoke object_program_pathname (the path name of the executable object) with any object_program_arguments (options or arguments to the program).  Use -- before object_program_arguments if your program takes an option that is the same as an option to the dde command (for example, an X Window System option).  If you do not use --, the option is interpreted as an option to the dde command, even if it appears after the program invocation. 

−attach process_id [object_program_pathname]
Attach to a program that is already running.  The process_id must be a UNIX pid, which you can obtain by using the ps(1) command.  The object_program_pathname specifies the path name of the program object module; use this option if your current directory is not the same as that of the program object module.  You must have the same user ID as the running program (or be logged in as root) in order to attach.  You cannot attach to a process if it is already being debugged. 

core_file object_program_pathname
Inspect the core file that an aborted program produced. core_file specifies the path name of the core file, and object_program_pathname specifies the path name of the program object module that aborted. 

EXAMPLES

Invoke the debugger, but do not invoke a target program:

dde

Debug the executable a.out:

dde a.out

Debug a.out, causing the debugger to print in the transcript area all input that it receives from the graphical interface:

dde -do ’property echo -graphic’ a.out

Debug the executable test, which takes the argument −d:

dde test -d

RUNNING THE DEBUGGER REMOTELY

You can use resources provided by the X Window System to run the debugger on one system while displaying the user interface on another. 

You can invoke the debugger remotely by performing the following steps:

1. To provide display access, enter the following at a shell prompt on the machine that will run the user interface:

xhost debugger_system

where debugger_system is the hostname of the system that will run the debugger.  The hostnames are usually listed in /etc/hosts. 

2. From the machine that will run the display, log in to the machine that will run the debugger. 

Typically, you would enter:

rlogin debugger_system

at a shell prompt, where debugger_system is the name of the system that will run the debugger. 

3. From the shell where you logged into the debugger_system, enter:

dde -display display_system:0

where display_system is the name of the system that will display the interface.  If you get a message stating that the dde command cannot be found, add /opt/langtools/bin to your PATH variable. 

EXTERNAL INFLUENCES

Native Language Support

LANG This variable determines the locale in which messages are displayed.  The default value for this variable is C. 

LC_CTYPE This variable determines the interpretation of text as single- and/or multi-byte characters and their printability when reading or writing character and string data.  If LC_CTYPE is not specified in the environment or is set to the empty string, the value of LANG is used as the default. 

International Code Set Support

Single byte and multi-byte character code sets are supported. 

FILES

/opt/langtools/bin/dde Main debugger executable. 

/opt/langtools/share/man
Man page directory.

/opt/langtools/lib/end.o
Auxiliary object file (support module) linked with all debuggable programs.

/opt/langtools/bin/pxdb The debug information preprocessor. 

/opt/langtools/dde/nls/C/app-defaults/DDE
Default X resources.

$HOME/.dderc The dde startup command file. The debugger first searches for .dderc in your current working directory and then in your $HOME directory. 

/opt/langtools/dde/contrib/dderc_xdb
Sample aliases for xdb commands. 

/opt/langtools/dde/contrib/dderc_threads
Sample aliases and customizations that are useful when debugging multi-threaded applications.

/opt/langtools/dde/contrib/dderc_hints
Examples of specialized macros.

/opt/langtools/dde/contrib/dderc_abbrev
Sample aliases that are shortcuts for HP/DDE commands.

/opt/langtools/dde/contrib/dbx_macros
Macros that simulate dbx syntax. 

/opt/langtools/dde/examples/*
Source files for the sample program average in C, FORTRAN, Pascal, and C++. 

SEE ALSO

adb(1), cc(1), CC(1), f77(1), ld(1), pc(1), multibyte(3C), shl_load(3X), system(3S), a.out(4), core(4), user(4), lang(5), signal(5)

HP/DDE Debugger User’s Guide
HP/DDE Debugger Reference

Hewlett-Packard Company  —  HP/DDE Version 3.2: June 1995

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026