What's new with GDB

GDB has had many bug fixes, particularly in the support of various remote targets.

Please note that, although the GDB version number is `4.14-95q4', the code is nearly identical to FSF GDB 4.15. There will be some differences, but they are minor, and this release has features, such as AIX 4.1 support, that are not in 4.15.

For the complete matrix of supported hosts vs. targets, see section Cygnus Developer's Kit: Progressive--95q4. Contact us at +1-800 CYGNUS-1 if you have any questions.

• $_exitcode There is a new convenience variable $_exitcode that is set to the value of the termination code returned when an inferior process exits.
• quit The quit command now accepts an optional argument that is the error code that GDB will return when it exits.
• load The load command in the I960-NINDY configuration now runs much faster.
• Data cache for remote targets Remote targets now use a data cache to speed up communication with the remote side. The data cache could lead to incorrect results because it doesn't know about volatile variables, thus making it impossible to debug targets which use memory mapped I/O devices. Use set remotecache off to turn the data cache off.
• Support for multiple threads The standard remote protocol now includes support for multiple threads in the target system, using new protocol commands H and T. See `gdb/remote.c' for details.
• --enable-netrom If GDB is configured with --enable-netrom, then it will include support for the NetROM ROM emulator from XLNT Designs. The NetROM acts as though it is a bank of ROM on the target board, but you can write into it over the network. GDB's support consists only of support for fast loading into the emulated ROM; to debug, you must use another protocol, such as standard remote protocol. The usual sequence is:

  target nrom <netrom-hostname>
  load <prog>
  target remote <netrom-hostname>:1235