gdb bug fix update

An updated gdb package that fixes various bugs is now available.

The GNU debugger, gdb, allows the debugging of programs written in C, C++,
and other languages by executing them in a controlled fashion and then
printing out their data.

This updated package addresses the following issues:

* Placing a breakpoint to program having some parts compiled without
debugging information (as provided by "gcc -g") could put the breakpoint at
incorrect place. The updated GDB places the breakpoint where the user
requested even for code without debugging information present. Note: the
program still must not have been stripped by the strip program. (BZ#442888)

* Debugging code compiled by the default C compiler of RHEL-4 (gcc) could
cause a GDB segmentation fault if the debugging information incorrectly
references a frame base which is not being defined by this debugging
information. The updated GDB writes an error message and continues to run.
Such code can be debugged correctly by using the alternative RHEL-4 C
compiler gcc4. (BZ#466222)

* On s390 and s390x architectures loading a core file of program using
shared libraries currently being prelinked at a different address than in
the time of the core dump could make the library not available for
investigation. The different address of a shared library may occur due to a
new prelink run from crond or by transferring the core file from a
different machine. The updated GDB properly displays the shared library
code for debugging notwithstanding its current prelinked address.
(BZ#468213)

* GDB could not backtrace through signal handler for i386 processes on
x86_64 kernel running on AMD CPUs. vDSO32 uses there a syscall instruction
for performance reasons which was not used on native i386 systems before.
The update GDB properly backtraces through signal handler even in this
case. (BZ#485508)

All users of gdb should upgrade to this updated package, which contains
backported patches to resolve these issues.

Before applying this update, make sure that all previously-released
errata relevant to your system have been applied.

This update is available via Red Hat Network. Details on how to use
the Red Hat Network to apply this update are available at
http://kbase.redhat.com/faq/docs/DOC-11259

442888 - gdb terminates with a segfault when stepping though a test application
466222 - gdb fails to set breakpoints