GNU gdb etc...

    libbfd.a libiberty.a, libmmalloc.a, libopcodes.a, libreadline.a

    bfd.h, ansidecl.h, obstack.h, readline/*.h

Changes in GDB-4.14:

• Alpha OSF/1 support for procfs
  GDB now supports procfs under OSF/1-2.x and higher, which makes it possible to attach to running processes. As the mounting of the /proc filesystem is optional on the Alpha, GDB automatically determines the availability of /proc during startup. This can lead to problems if /proc is unmounted after GDB has been started.

• Arguments to user-defined commands
  User commands may accept up to 10 arguments separated by whitespace. Arguments are accessed within the user command via $arg0..$arg9. A trivial example:

  define adder
    print $arg0 + $arg1 + $arg2
  
  To execute the command use:
  adder 1 2 3
  

  Defines the command "adder" which prints the sum of its three arguments. Note the arguments are text substitutions, so they may reference variables, use complex expressions, or even perform inferior function calls.

• New `if' and `while' commands
  This makes it possible to write more sophisticated user-defined commands. Both commands take a single argument, which is the expression to evaluate, and must be followed by the commands to execute, one per line, if the expression is nonzero, the list being terminated by the word `end'. The `if' command list may include an `else' word, which causes the following commands to be executed only if the expression is zero.

• Fortran source language mode
  GDB now includes partial support for Fortran 77. It will recognize Fortran programs and can evaluate a subset of Fortran expressions, but variables and functions may not be handled correctly. GDB will work with G77, but does not yet know much about symbols emitted by other Fortran compilers.

• Target byte order now dynamically selectable
  You can choose which byte order to use with a target system, via the commands "set endian big" and "set endian little", and you can see the current setting by using "show endian". You can also give the command "set endian auto", in which case GDB will use the byte order associated with the executable. Currently, only embedded MIPS configurations support dynamic selection of target byte order.

The latest version of GNU debugger has been installed on all exp trees (AIX, Digital Unix (formerly OSF/1), HP-UX, IRIX, Solaris, SUN, and Ultrix). It should be available on both exp server tomorrow (Jan. 5).
The current program/library will add a -4.14 suffix. The affected files are:

Installed files                 Previous files
/exp/rcf/share/bin
gdb                             gdb-4.14

/exp/rcf/share/lib
libreadline.a                   libreadline-4.14.a
libmmalloc.a                    libmmalloc-4.14.a
(the followin libraries will be reinstalled but the content should be,
 the same. (from the same source code))
libopcodes.a
libiberty.a
libbfd.a

/exp/rcf/share/include
readline                        readline-4.14

• Under Ultrix 4.2 (DECstation-3100) or Alphas under OSF/1, we have seen problems with backtraces after interrupting the inferior out of a read(). The problem is caused by ptrace() returning an incorrect value for the frame pointer register (register 15 or 30). As far as we can tell, this is a kernel problem. Any help with this would be greatly appreciated.
• Under Ultrix 4.4 (DECstation-3100), setting the TERMCAP environment variable to a string without a trailing ':' can cause GDB to dump core upon startup. Although the core file makes it look as though GDB code failed, the crash actually occurs within a call to the termcap library function tgetent(). The problem can be solved by using the GNU Termcap library. Alphas running OSF/1 (versions 1.0 through 2.1) have the same buggy termcap code, but GDB behaves strangely rather than crashing.
• On DECstations there are warnings about shift counts out of range in various BFD modules. None of them is a cause for alarm, they are actually a result of bugs in the DECstation compiler.
• Notes for the DEC Alpha using OSF/1: The debugging output of native cc has two known problems; we view these as compiler bugs. The linker miscompacts symbol tables, which causes gdb to confuse the type of variables or results in `struct < illegal >' type outputs. dbx has the same problems with those executables. A workaround is to specify -Wl,-b when linking, but that will increase the executable size considerably. If a structure has incomplete type in one file (e.g., "struct foo *" without a definition for "struct foo"), gdb will be unable to find the structure definition from another file. It has been reported that the Ultrix 4.3A compiler on decstations has the same problems.
• Notes for Solaris 2.x, using the SPARCworks cc compiler: You have to compile your program with the -xs option of the SPARCworks compiler to be able to debug your program with gdb. Under Solaris 2.3 you also need patch 101409-03 (Jumbo linker patch). Under Solaris 2.2, if you have patch 101052 installed, make sure that it is at least at revision 101052-06.
• Under Irix 5 for SGIs, you must have installed the `compiler_dev.hdr' subsystem that is on the IDO CD, otherwise you will get complaints that certain files such as `/usr/include/syms.h' cannot be found.