---------
GDB 7.6.1 provides the following fixes and improvements to GDB 7.6:
* PR tdep/15420 (Cannot debug threaded programs on newer versions
of x86-solaris - Solaris 10, Update 10 or later)
* PR remote/15455 (QTro remote packet broken)
* PR build/15476 (Build failure due to incomplete enum type in utils.h)
* PR server/15594 (tls support in 64x32 x86 gdbserver doesn't extend
address to 64 bit)
* PR server/15075 (dprintf inteferes with "next")
* PR server/15434 (dprintf uses a synchronous 'continue' even in
non-stop mode)
* PR tui/14880 (in split register layouts, up results in assertion
failure in value.c)
* PR c++/15519 (GDB 7.6 is 94x slower than GDB 7.5.1 using a certain
core file)
* PR gdb/15837 (GDB prints entry values for local variables)
* PR gdb/15415 (gdb resolves symbolic links when passing argv[0])
* PR cli/15603 (CTRL-C can no longer interrupt inferior)
* PR gdb/15604 (gdbserver socket leak 7.5 regression)
---------
Add patch-opcodes_configure to avoid build error
(at least on NetBSD/amd64 6.1).
---
http://www.gnu.org/software/gdb/news/
April 26th, 2013: GDB 7.6 Released!
Changes in this release include:
- New native configurations (ARM AArch64 GNU/Linux,
FreeBSD/powerpc, 86_64/Cygwin and Tilera TILE-Gx
GNU/Linux)
- New target configurations (ARM AArch64, ARM AArch64
GNU/Linux, Lynx 178 PowerPC, x86_64/Cygwin, and Tilera
TILE-Gx GNU/Linux)
- Support for the "mini debuginfo" section, .gnu_debugdata
- The C++ ABI now defaults to the GNU v3 ABI
- More Python scripting improvements
- Some GDB/MI improvements
- New configure options, new commands, and options
- New remote packets
- A new "target record-btrace" has been added while the
"target record" command has been renamed to "target
record-full"
See the NEWS file for a more complete and detailed list of what this release includes.
- Move DragonFly setup lines into conditional.
- Add TEST_ENV= line for 'make test' target.
(2) files/dragonfly-default.exp
- Have compiler environment for 'make test' target in
this file (refered from Makefile TEST_ENV).
(3) TODO
- Add results of 'make test' on DragonFly/i386
The purpose of a debugger such as GDB is to allow you to see what
is going on "inside" another program while it executes--or what
another program was doing at the moment it crashed.
GDB can do four main kinds of things (plus other things in support
of these) to help you catch bugs in the act:
* Start your program, specifying anything that might affect its
behavior.
* Make your program stop on specified conditions.
* Examine what has happened, when your program has stopped.
* Change things in your program, so you can experiment with
correcting the effects of one bug and go on to learn about
another.
