What has changed in GDB?
(Organized release by release)
-*** Changes since GDB 6.1:
+*** Changes since GDB 6.2:
+
+*** Changes in GDB 6.2:
+
+* Fix for ``many threads''
+
+On GNU/Linux systems that use the NPTL threads library, a program
+rapidly creating and deleting threads would confuse GDB leading to the
+error message:
+
+ ptrace: No such process.
+ thread_db_get_info: cannot get thread info: generic error
+
+This problem has been fixed.
+
+* "-async" and "-noasync" options removed.
+
+Support for the broken "-noasync" option has been removed (it caused
+GDB to dump core).
* New ``start'' command.
call; backtrace through a signal trampoline; step into and out of
signal handlers; and single-stepping in the signal trampoline.
-These fixes were tested on i386 GNU/Linux systems that include a 2.4
-kernel.
+Please note that kernel bugs are a limiting factor here. These
+features have been shown to work on an s390 GNU/Linux system that
+include a 2.6.8-rc1 kernel. Ref PR breakpoints/1702.
* Cygwin support for DWARF 2 added.
NetBSD/vax vax-*-netbsd*
OpenBSD/vax vax-*-openbsd*
+* END-OF-LIFE frame compatibility module
+
+GDB's internal frame infrastructure has been completely rewritten.
+The new infrastructure making it possible to support key new features
+including DWARF 2 Call Frame Information. To aid in the task of
+migrating old configurations to this new infrastructure, a
+compatibility module, that allowed old configurations to continue to
+work, was also included.
+
+GDB 6.2 will be the last release to include this frame compatibility
+module. This change directly impacts the following configurations:
+
+h8300-*-*
+mcore-*-*
+mn10300-*-*
+ns32k-*-*
+sh64-*-*
+v850-*-*
+xstormy16-*-*
+
+Unless there is activity to revive these configurations, they will be
+made OBSOLETE in GDB 6.3, and REMOVED from GDB 6.4.
+
* REMOVED configurations and files
Sun 3, running SunOS 3 m68*-*-sunos3*