(ddd.info)Choosing an Inferior Debugger

---

Next: Options Up: Invoking

---

Enter node , (file) or (file)node

2.1.1 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 Bash, Java,
     GNU Make, Perl, or Python, then you should use a Bash, JDB, GNU
     Make, Perl, `pydb', Bash, or inferior debugger.

     Use

          ddd --bash PROGRAM
          ddd --interpreter='_path-to-debugger-bash_ --debugger' PROGRAM

          ddd --jdb PROGRAM

          ddd --make PROGRAM
          ddd --interpreter='_path-to-debugger-make_ --debugger' PROGRAM

          ddd --perl PROGRAM

          ddd --pydb PROGRAM

     to run DDD with JDB, `pydb', Perl, Bash, or GNU Make as an inferior
     debugger.

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

     Use

          ddd --dbx PROGRAM

          ddd --gdb PROGRAM

          ddd --ladebug PROGRAM

          ddd --wdb PROGRAM

          ddd --xdb 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 PROGRAM
to analyze, then DDD will automatically determine the inferior debugger:

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

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

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