Invoking DDD

Normally, you can run DDD by invoking the program ddd.

You can also run DDD with a variety of arguments and options, to specify more of your debugging environment at the outset.

The most usual way to start DDD is with one argument, specifying an executable program:

     ddd 

**Illegal HTML tag removed :** program

     

If you use GDB, DBX, Ladebug, or XDB as inferior debuggers, you can also start with both an executable program and a core file specified:

     ddd 

**Illegal HTML tag removed :** program

**Illegal HTML tag removed :** core

     

You can, instead, specify a process ID as a second argument, if you want to debug a running process:

     ddd 

**Illegal HTML tag removed :** program

 1234
     

would attach DDD to process 1234 (unless you also have a file named 1234; DDD does check for a core file first).

You can further control DDD by invoking it with specific Illegal HTML tag removed : options. To get a list of DDD options, invoke DDD as

     ddd --help
     

Most important are the options to specify the inferior debugger (see Choosing an Inferior Debugger), but you can also customize several aspects of DDD upon invocation (see Options).

DDD also understands the usual X options such as -display or -geometry. See X Options, for details.

All arguments and options that are not understood by DDD are passed to the inferior debugger; See Inferior Debugger Options, for a survey. To pass an option to the inferior debugger that conflicts with an X option, or with a DDD option listed here, use the --debugger option (see Options).

• Choosing an Inferior Debugger: Which debugger to use?
• Options: How to invoke DDD
• X Options: Setting X properties
• Inferior Debugger Options: Customizing GDB, DBX, and so on
• Multiple Instances: Running multiple DDD instances
• X Warnings: Turning off obnoxious warnings

Node:Choosing an Inferior Debugger, Next:Options, Up:Invoking

Choosing an Inferior Debugger

The most frequently required options are those to choose a specific inferior debugger.

Normally, the inferior debugger is determined by the program to analyze:

• If the program requires a specific interpreter, such as Java, Python, Perl or Bash, then you should use a JDB, PYDB, Perl, or Bash inferior debugger.

  Use

            ddd --jdb 
  
  **Illegal HTML tag removed :** program
  
            

            ddd --pydb 
  
  **Illegal HTML tag removed :** program
  
            

            ddd --perl 
  
  **Illegal HTML tag removed :** program
  
            

            ddd --bash 
  
  **Illegal HTML tag removed :** program
  
            ddd --interpreter='_path-to-debugger-bash_ --debugger' 
  
  **Illegal HTML tag removed :** program
  
            

  to run DDD with JDB, PYDB, Perl, or Bash as an inferior debugger.

• If the program is an executable binary, you should use GDB, DBX, Ladebug, or XDB. In general, GDB (or its HP variant, WDB) provides the most functionality of these debuggers.

  Use

            ddd --gdb 
  
  **Illegal HTML tag removed :** program
  
            

            ddd --wdb 
  
  **Illegal HTML tag removed :** program
  
            

            ddd --dbx 
  
  **Illegal HTML tag removed :** program
  
            

            ddd --ladebug 
  
  **Illegal HTML tag removed :** program
  
            

            ddd --xdb 
  
  **Illegal HTML tag removed :** program
  
            

  to run DDD with GDB, WDB, DBX, Ladebug, or XDB as inferior debugger.

If you invoke DDD without any of these options, but give a Illegal HTML tag removed : program to analyze, then DDD will automatically determine the inferior debugger:

• If

  Illegal HTML tag removed : program

  is a Python program, a Perl script, or a Java class, DDD will invoke the appropriate debugger.

• If

  Illegal HTML tag removed : program

  is an executable binary, DDD will invoke its default debugger for executables (usually GDB).

See Customizing Debugger Interaction, for more details on determining the inferior debugger.

Node:Options, Next:X Options, Previous:Choosing an Inferior Debugger, Up:Invoking

DDD Options

You can further control how DDD starts up using the following options. All options may be abbreviated, as long as they are unambiguous; single dashes - instead of double dashes -- may also be used. Almost all options control a specific DDD resource or resource class (see Customizing).

• --attach-windows

• Attach the source and data windows to the debugger console, creating one single big DDD window. This is the default setting.

  Giving this option is equivalent to setting the DDD Separate resource class to off. See Window Layout, for details.

• --attach-source-window

• Attach only the source window to the debugger console.

  Giving this option is equivalent to setting the DDD separateSourceWindow resource to off. See Window Layout, for details.

• --attach-data-window

• Attach only the source window to the debugger console.

  Giving this option is equivalent to setting the DDD separateDataWindow resource to off. See Window Layout, for details.

• --automatic-debugger

• Determine the inferior debugger automatically from the given arguments.

  Giving this option is equivalent to setting the DDD autoDebugger resource to on. See Customizing Debugger Interaction, for details.

• --button-tips

• Enable button tips.

  Giving this option is equivalent to setting the DDD buttonTips resource to on. See Customizing Help, for details.

• --configuration

• Print the DDD configuration settings on standard output and exit.

  Giving this option is equivalent to setting the DDD showConfiguration resource to on. See Diagnostics, for details.

• --check-configuration

• Check the DDD environment (in particular, the X configuration), report any possible problem causes and exit.

  Giving this option is equivalent to setting the DDD checkConfiguration resource to on. See Diagnostics, for details.

• --data-window

• Open the data window upon start-up.

  Giving this option is equivalent to setting the DDD openDataWindow resource to on. See Toggling Windows, for details.

• --dbx

• Run DBX as inferior debugger.

  Giving this option is equivalent to setting the DDD debugger resource to dbx. See Customizing Debugger Interaction, for details.

• --debugger

  Illegal HTML tag removed : name

• Invoke the inferior debugger

  Illegal HTML tag removed : name

  . This is useful if you have several debugger versions around, or if the inferior debugger cannot be invoked under its usual name (i.e. gdb, wdb, dbx, xdb, jdb, pydb, or perl).

  This option can also be used to pass options to the inferior debugger that would otherwise conflict with DDD options. For instance, to pass the option -d Illegal HTML tag removed : directory to XDB, use:

            ddd --debugger "xdb -d 
  
  **Illegal HTML tag removed :** directory
  
  "
            

  If you use the --debugger option, be sure that the type of inferior debugger is specified as well. That is, use one of the options --gdb, --dbx, --xdb, --jdb, --pydb, or --perl (unless the default setting works fine).

  Giving this option is equivalent to setting the DDD debuggerCommand resource to Illegal HTML tag removed : name. See Customizing Debugger Interaction, for details.

• --debugger-console

• Open the debugger console upon start-up.

  Giving this option is equivalent to setting the DDD openDebuggerConsole resource to on. See Toggling Windows, for details.

• --disassemble

• Disassemble the source code. See also the --no-disassemble option, below.

  Giving this option is equivalent to setting the DDD disassemble resource to on. See Customizing Source, for details.

• --exec-window

• Run the debugged program in a specially created execution window. This is useful for programs that have special terminal requirements not provided by the debugger window, as raw keyboard processing or terminal control sequences. See Using the Execution Window, for details.

  Giving this option is equivalent to setting the DDD separateExecWindow resource to on. See Customizing the Execution Window, for details.

• --font

  Illegal HTML tag removed : fontname

• -fn

  Illegal HTML tag removed : fontname

• Use

  Illegal HTML tag removed : fontname

  as default font.

  Giving this option is equivalent to setting the DDD defaultFont resource to fontname. See Customizing Fonts, for details.

• --fonts

• Show the font definitions used by DDD on standard output.

  Giving this option is equivalent to setting the DDD showFonts resource to on. See Diagnostics, for details.

• --fontsize

  Illegal HTML tag removed : size

• Set the default font size to

  Illegal HTML tag removed : size

  (in 1/10 points). To make DDD use 12-point fonts, say --fontsize 120.

  Giving this option is equivalent to setting the DDD FontSize resource class to size. See Customizing Fonts, for details.

• --fullname

• -f

• Enable the TTY interface, taking additional debugger commands from standard input and forwarding debugger output on standard output. Current positions are issued in GDB -fullname format suitable for debugger front-ends. By default, both the debugger console and source window are disabled. See TTY mode, for a discussion.

  Giving this option is equivalent to setting the DDD TTYMode resource class to on. See TTY mode, for details.

• --gdb

• Run GDB as inferior debugger.

  Giving this option is equivalent to setting the DDD debugger resource to gdb. See Customizing Debugger Interaction, for details.

• --glyphs

• Display the current execution position and breakpoints as glyphs. See also the --no-glyphs option, below.

  Giving this option is equivalent to setting the DDD displayGlyphs resource to on. See Customizing Source, for details.

• --help

• -h
• -?

• Give a list of frequently used options. Show options of the inferior debugger as well.

  Giving this option is equivalent to setting the DDD showInvocation resource to on. See Diagnostics, for details.

• --host

  Illegal HTML tag removed : hostname

• --host

  Illegal HTML tag removed : username

  @

  Illegal HTML tag removed : hostname

• Invoke the inferior debugger directly on the remote host

  Illegal HTML tag removed : hostname

  . If

  Illegal HTML tag removed : username

  is given and the --login option is not used, use

  Illegal HTML tag removed : username

  as remote user name. See Remote Debugger, for details.

  Giving this option is equivalent to setting the DDD debuggerHost resource to Illegal HTML tag removed : hostname. See Remote Debugger, for details.

• --jdb

• Run JDB as inferior debugger.

  Giving this option is equivalent to setting the DDD debugger resource to gdb. See Customizing Debugger Interaction, for details.

• --ladebug

• Run Ladebug as inferior debugger.

  Giving this option is equivalent to setting the DDD debugger resource to ladebug. See Customizing Debugger Interaction, for details.

• --lesstif-hacks

• Equivalent to --lesstif-version 999. Deprecated.

  Giving this option is equivalent to setting the DDD lessTifVersion resource to 999. See LessTif, for details.

• --lesstif-version

  Illegal HTML tag removed : version

• Enable some hacks to make DDD run properly with LessTif. See LessTif, for a discussion.

  Giving this option is equivalent to setting the DDD lessTifVersion resource to Illegal HTML tag removed : version. See LessTif, for details.

• --license

• Print the DDD license on standard output and exit.

  Giving this option is equivalent to setting the DDD showLicense resource to Illegal HTML tag removed : on. See Diagnostics, for details.

• --login

  Illegal HTML tag removed : username

• -l

  Illegal HTML tag removed : username

• Use

  Illegal HTML tag removed : username

  as remote user name. See Remote Debugger, for details.

  Giving this option is equivalent to setting the DDD debuggerHostLogin resource to Illegal HTML tag removed : username. See Remote Debugger, for details.

• --maintenance

• Enable the top-level Maintenance menu with options for debugging DDD. See Maintenance Menu, for details.

  Giving this option is equivalent to setting the DDD maintenance resource to Illegal HTML tag removed : on. See Maintenance Menu, for details.

• --manual

• Print the DDD manual on standard output and exit.

  Giving this option is equivalent to setting the DDD showManual resource to Illegal HTML tag removed : on. See Diagnostics, for details.

• --news

• Print the DDD news on standard output and exit.

  Giving this option is equivalent to setting the DDD showNews resource to Illegal HTML tag removed : on. See Diagnostics, for details.

• --no-button-tips

• Disable button tips.

  Giving this option is equivalent to setting the DDD buttonTips resource to off. See Customizing Help, for details.

• --no-data-window

• Do not open the data window upon start-up.

  Giving this option is equivalent to setting the DDD openDataWindow resource to off. See Toggling Windows, for details.

• --no-debugger-console

• Do not open the debugger console upon start-up.

  Giving this option is equivalent to setting the DDD openDebuggerConsole resource to off. See Toggling Windows, for details.

• --no-disassemble

• Do not disassemble the source code.

  Giving this option is equivalent to setting the DDD disassemble resource to off. See Customizing Source, for details.

• --no-exec-window

• Do not run the debugged program in a specially created execution window; use the debugger console instead. Useful for programs that have little terminal input/output, or for remote debugging. See Using the Execution Window, for details.

  Giving this option is equivalent to setting the DDD separateExecWindow resource to off. See Customizing the Execution Window, for details.

• --no-glyphs

• Do not use glyphs; display the current execution position and breakpoints as text characters.

  Giving this option is equivalent to setting the DDD displayGlyphs resource to off. See Customizing Source, for details.

• --no-lesstif-hacks

• Equivalent to --lesstif-version 1000. Deprecated.

  Giving this option is equivalent to setting the DDD lessTifVersion resource to 1000. See LessTif, for details.

• --no-maintenance

• Do not enable the top-level Maintenance menu with options for debugging DDD. This is the default. See Maintenance Menu, for details.

  Giving this option is equivalent to setting the DDD maintenance resource to Illegal HTML tag removed : off. See Maintenance Menu, for details.

• --no-source-window

• Do not open the source window upon start-up.

  Giving this option is equivalent to setting the DDD openSourceWindow resource to off. See Toggling Windows, for details.

• --no-value-tips

• Disable value tips.

  Giving this option is equivalent to setting the DDD valueTips resource to off. See Value Tips, for details.

• --nw

• Do not use the X window interface. Start the inferior debugger on the local host.
• --perl

• Run Perl as inferior debugger.

  Giving this option is equivalent to setting the DDD debugger resource to perl. See Customizing Debugger Interaction, for details.

• --pydb

• Run PYDB as inferior debugger.

  Giving this option is equivalent to setting the DDD debugger resource to pydb. See Customizing Debugger Interaction, for details.

• --panned-graph-editor

• Use an Athena panner to scroll the data window. Most people prefer panners on scroll bars, since panners allow two-dimensional scrolling. However, the panner is off by default, since some M*tif implementations do not work well with Athena widgets. See Display Resources, for details; see also --scrolled-graph-editor, below.

  Giving this option is equivalent to setting the DDD pannedGraphEditor resource to on. See Display Resources, for details.

• --play-log

  Illegal HTML tag removed : log-file

• Recapitulate a previous DDD session.

            ddd --play-log 
  
  **Illegal HTML tag removed :** log-file
  
            

  invokes DDD as inferior debugger, simulating the inferior debugger given in Illegal HTML tag removed : log-file (see below). This is useful for debugging DDD.

  Giving this option is equivalent to setting the DDD playLog resource to on. See Customizing Debugger Interaction, for details.

• --PLAY

  Illegal HTML tag removed : log-file

• Simulate an inferior debugger.

  Illegal HTML tag removed : log-file

  is a ~/.ddd/log file as generated by some previous DDD session (see Logging). When a command is entered, scan

  Illegal HTML tag removed : log-file

  for this command and re-issue the logged reply; if the command is not found, do nothing. This is used by the --play option.

• --rhost

  Illegal HTML tag removed : hostname

• --rhost

  Illegal HTML tag removed : username

  @

  Illegal HTML tag removed : hostname

• Run the inferior debugger interactively on the remote host

  Illegal HTML tag removed : hostname

  . If

  Illegal HTML tag removed : username

  is given and the --login option is not used, use

  Illegal HTML tag removed : username

  as remote user name. See Remote Debugger, for details.

  Giving this option is equivalent to setting the DDD debuggerRHost resource to Illegal HTML tag removed : hostname. See Remote Debugger, for details.

• --scrolled-graph-editor

• Use M*tif scroll bars to scroll the data window. This is the default in most DDD configurations. See Display Resources, for details; see also --panned-graph-editor, above.

  Giving this option is equivalent to setting the DDD pannedGraphEditor resource to off. See Display Resources, for details.

• --separate-windows

• --separate

• Separate the console, source and data windows. See also the --attach options, above.

  Giving this option is equivalent to setting the DDD Separate resource class to off. See Window Layout, for details.

• --session

  Illegal HTML tag removed : session

• Load

  Illegal HTML tag removed : session

  upon start-up. See Resuming Sessions, for details.

  Giving this option is equivalent to setting the DDD session resource to Illegal HTML tag removed : session. See Resuming Sessions, for details.

• --source-window

• Open the source window upon start-up.

  Giving this option is equivalent to setting the DDD openSourceWindow resource to on. See Toggling Windows, for details.

• --status-at-bottom

• Place the status line at the bottom of the source window.

  Giving this option is equivalent to setting the DDD statusAtBottom resource to on. See Window Layout, for details.

• --status-at-top

• Place the status line at the top of the source window.

  Giving this option is equivalent to setting the DDD statusAtBottom resource to off. See Window Layout, for details.

• --sync-debugger

• Do not process X events while the debugger is busy. This may result in slightly better performance on single-processor systems.

  Giving this option is equivalent to setting the DDD synchronousDebugger resource to on. See Customizing Debugger Interaction, for details.

• --toolbars-at-bottom

• Place the toolbars at the bottom of the respective window.

  Giving this option is equivalent to setting the DDD toolbarsAtBottom resource to on. See Window Layout, for details.

• --toolbars-at-top

• Place the toolbars at the top of the respective window.

  Giving this option is equivalent to setting the DDD toolbarsAtBottom resource to off. See Window Layout, for details.

• --trace

• Show the interaction between DDD and the inferior debugger on standard error. This is useful for debugging DDD. If --trace is not specified, this information is written into ~/.ddd/log (~ stands for your home directory), such that you can also do a post-mortem debugging. See Logging, for details about logging.

  Giving this option is equivalent to setting the DDD trace resource to Illegal HTML tag removed : on. See Diagnostics, for details.

• --tty

• -t

• Enable TTY interface, taking additional debugger commands from standard input and forwarding debugger output on standard output. Current positions are issued in a format readable for humans. By default, the debugger console is disabled.

  Giving this option is equivalent to setting the DDD ttyMode resource to on. See TTY mode, for details.

• --value-tips

• Enable value tips.

  Giving this option is equivalent to setting the DDD valueTips resource to on. See Value Tips, for details.

• --version

• -v

• Print the DDD version on standard output and exit.

  Giving this option is equivalent to setting the DDD showVersion resource to on. See Diagnostics, for details.

• --vsl-library

  Illegal HTML tag removed : library

• Load the VSL library

  Illegal HTML tag removed : library

  instead of using the DDD built-in library. This is useful for customizing display shapes and fonts.

  Giving this option is equivalent to setting the DDD vslLibrary resource to Illegal HTML tag removed : library. See VSL Resources, for details.

• --vsl-path

  Illegal HTML tag removed : path

• Search VSL libraries in

  Illegal HTML tag removed : path

  (a colon-separated directory list).

  Giving this option is equivalent to setting the DDD vslPath resource to Illegal HTML tag removed : path. See VSL Resources, for details.

• --vsl-help

• Show a list of further options controlling the VSL interpreter. These options are intended for debugging purposes and are subject to change without further notice.
• --wdb

• Run WDB as inferior debugger.

  Giving this option is equivalent to setting the DDD debugger resource to wdb. See Customizing Debugger Interaction, for details.

• --xdb

• Run XDB as inferior debugger.

  Giving this option is equivalent to setting the DDD debugger resource to xdb. See Customizing Debugger Interaction, for details.

Node:X Options, Next:Inferior Debugger Options, Previous:Options, Up:Invoking

X Options

DDD also understands the following X options. Note that these options only take a single dash -.

• -display

  Illegal HTML tag removed : display

• Use the X server

  Illegal HTML tag removed : display

  . By default,

  Illegal HTML tag removed : display

  is taken from the DISPLAY environment variable.

• -geometry

  Illegal HTML tag removed : geometry

• Specify the initial size and location of the debugger console.

• -iconic
• Start DDD iconified.

• -name

  Illegal HTML tag removed : name

• Give DDD the name

  Illegal HTML tag removed : name

  .

• -selectionTimeout

  Illegal HTML tag removed : timeout

• Specify the timeout in milliseconds within which two communicating applications must respond to one another for a selection request.

• -title

  Illegal HTML tag removed : name

• Give the DDD window the title

  Illegal HTML tag removed : name

  .

• -xrm

  Illegal HTML tag removed : resourcestring

• Specify a resource name and value to override any defaults.

Node:Inferior Debugger Options, Next:Multiple Instances, Previous:X Options, Up:Invoking

Inferior Debugger Options

All options that DDD does not recognize are passed to the inferior debugger. This section lists the most useful options of the different inferior debuggers supported by DDD. In case these options do not work as expected, please lookup the appropriate reference.

• GDB Options:
• DBX and Ladebug Options:
• XDB Options:
• JDB Options:
• PYDB Options:
• Perl Options:
• Bash Options:

Node:GDB Options, Next:DBX and Ladebug Options, Up:Inferior Debugger Options

GDB Options

These GDB options are useful when using DDD with GDB as inferior debugger. Single dashes - instead of double dashes -- may also be used.

• -b

  Illegal HTML tag removed : baudrate

• Set serial port baud rate used for remote debugging.

• --cd

  Illegal HTML tag removed : dir

• Change current directory to

  Illegal HTML tag removed : dir

  .

• --command

  Illegal HTML tag removed : file

• Execute GDB commands from

  Illegal HTML tag removed : file

  .

• --core

  Illegal HTML tag removed : corefile

• Analyze the core dump

  Illegal HTML tag removed : corefile

  .

• --directory

  Illegal HTML tag removed : dir

• -d

  Illegal HTML tag removed : dir

• Add

  Illegal HTML tag removed : directory

  to the path to search for source files.

• --exec

  Illegal HTML tag removed : execfile

• Use

  Illegal HTML tag removed : execfile

  as the executable.

• --mapped
• Use mapped symbol files if supported on this system.
• --nx
• -n
• Do not read .gdbinit file.
• --readnow
• Fully read symbol files on first access.

• --se

  Illegal HTML tag removed : file

• Use

  Illegal HTML tag removed : file

  as symbol file and executable file.

• --symbols

  Illegal HTML tag removed : symfile

• Read symbols from

  Illegal HTML tag removed : symfile

  .

See Invoking GDB, for further options that can be used with GDB.

Node:DBX and Ladebug Options, Next:XDB Options, Previous:GDB Options, Up:Inferior Debugger Options

DBX and Ladebug Options

DBX variants differ widely in their options, so we cannot give a list here. Check out the dbx(1) and ladebug(1) manual pages.

Node:XDB Options, Next:JDB Options, Previous:DBX and Ladebug Options, Up:Inferior Debugger Options

XDB Options

These XDB options are useful when using DDD with XDB as inferior debugger.

• -d

  Illegal HTML tag removed : dir

• Specify

  Illegal HTML tag removed : dir

  as an alternate directory where source files are located.

• -P

  Illegal HTML tag removed : process-id

• Specify the process ID of an existing process the user wants to debug.

• -l

  Illegal HTML tag removed : library

• Pre-load information about the shared library

  Illegal HTML tag removed : library

  . -l ALL means always pre-load shared library information.

• -S

  Illegal HTML tag removed : num

• Set the size of the string cache to

  Illegal HTML tag removed : num

  bytes (default is 1024, which is also the minimum).

• -s
• Enable debugging of shared libraries.

Further options can be found in the xdb(1) manual page.

Node:JDB Options, Next:PYDB Options, Previous:XDB Options, Up:Inferior Debugger Options

JDB Options

JDB as of JDK 1.2

The following JDB options are useful when using DDD with JDB (from JDK 1.2) as inferior debugger.

• -attach

  Illegal HTML tag removed : address

• attach to a running virtual machine (VM) at

  Illegal HTML tag removed : address

  using standard connector

• -listen

  Illegal HTML tag removed : address

• wait for a running VM to connect at

  Illegal HTML tag removed : address

  using standard connector

• -listenany
• wait for a running VM to connect at any available address using standard connector
• -launch
• launch VM immediately instead of waiting for run command

These JDB options are forwarded to the debuggee:

• -verbose[:class|gc|jni]
• -v
• Turn on verbose mode.

• -D

  Illegal HTML tag removed : name

  =

  Illegal HTML tag removed : value

• Set the system property

  Illegal HTML tag removed : name

  to

  Illegal HTML tag removed : value

  .

• -classpath

  Illegal HTML tag removed : path

• List directories in which to look for classes.

  Illegal HTML tag removed : path

  is a list of directories separated by colons.

• -X

  Illegal HTML tag removed : option

• Non-standard target VM option

JDB as of JDK 1.1

The following JDB options are useful when using DDD with JDB (from JDK 1.1) as inferior debugger.

• -host

  Illegal HTML tag removed : hostname

• host machine of interpreter to attach to

• -password

  Illegal HTML tag removed : psswd

• password of interpreter to attach to (from -debug)

These JDB options are forwarded to the debuggee:

• -verbose
• -v
• Turn on verbose mode.
• -debug
• Enable remote Java debugging,
• -noasyncgc
• Don't allow asynchronous garbage collection.
• -verbosegc
• Print a message when garbage collection occurs.
• -noclassgc
• Disable class garbage collection.
• -checksource
• -cs
• Check if source is newer when loading classes.

• -ss

  Illegal HTML tag removed : number

• Set the maximum native stack size for any thread.

• -oss

  Illegal HTML tag removed : number

• Set the maximum Java stack size for any thread.

• -ms

  Illegal HTML tag removed : number

• Set the initial Java heap size.

• -mx

  Illegal HTML tag removed : number

• Set the maximum Java heap size.

• -D

  Illegal HTML tag removed : name

  =

  Illegal HTML tag removed : value

• Set the system property

  Illegal HTML tag removed : name

  to

  Illegal HTML tag removed : value

  .

• -classpath

  Illegal HTML tag removed : path

• List directories in which to look for classes.

  Illegal HTML tag removed : path

  is a list of directories separated by colons.

• -prof

• -prof:

  Illegal HTML tag removed : file

• Output profiling data to ./java.prof. If

  Illegal HTML tag removed : file

  is given, write the data to ./

  Illegal HTML tag removed : file

  .

• -verify
• Verify all classes when read in.
• -verifyremote
• Verify classes read in over the network (default).
• -noverify
• Do not verify any class.
• -dbgtrace
• Print info for debugging JDB.

Further options can be found in the JDB documentation.

Node:PYDB Options, Next:Perl Options, Previous:JDB Options, Up:Inferior Debugger Options

PYDB Options

For a list of useful PYDB options, check out the PYDB documentation.

Node:Perl Options, Next:Bash Options, Previous:PYDB Options, Up:Inferior Debugger Options

Perl Options

The most important Perl option to use with DDD is -w; it enables several important warnings. For further options, see the perlrun(1) manual page.

Node:Bash Options, Previous:Perl Options, Up:Inferior Debugger Options

Bash Options

If you have the proper bash installed, the option needed to specify debugging support is --debugger. (If your bash doesn't understand this option you need to pick up a version of bash that does from http://bashdb.sourceforge.net.)

Node:Multiple Instances, Next:X Warnings, Previous:Inferior Debugger Options, Up:Invoking

Multiple DDD Instances

If you have multiple DDD instances running, they share common preferences and history files. This means that changes applied to one instance may get lost when being overwritten by the other instance. DDD has two means to protect you against unwanted losses. The first means is an automatic reloading of changed options, controlled by the following resource (see Customizing):

Normally, automatic reloading of options should already suffice. If you need stronger protection, DDD also provides a warning against multiple instances. This warning is disabled by default, If you want to be warned about multiple DDD invocations sharing the same preferences and history files, enable Edit => Preferences => Warn if Multiple DDD Instances are Running.

This setting is tied to the following resource (see Customizing):

Node:X Warnings, Previous:Multiple Instances, Up:Invoking

X warnings

If you are bothered by X warnings, you can suppress them by setting Edit => Preferences => General => Suppress X warnings.

This setting is tied to the following resource (see Customizing):

Node:Quitting, Next:Sessions, Previous:Invoking, Up:Invocation