What has changed in GDB?
(Organized release by release)
-*** Changes since GDB 7.2
+*** Changes since GDB 7.3
+
+*** Changes in GDB 7.3
* GDB has a new command: "thread find [REGEXP]".
It finds the thread id whose name, target id, or thread extra info
* Python scripting
+ ** The function gdb.Write now accepts an optional keyword 'stream'.
+ This keyword, when provided, will direct the output to either
+ stdout, stderr, or GDB's logging output.
+
+ ** Parameters can now be be sub-classed in Python, and in particular
+ you may implement the get_set_doc and get_show_doc functions.
+ This improves how Parameter set/show documentation is processed
+ and allows for more dynamic content.
+
+ ** Symbols, Symbol Table, Symbol Table and Line, Object Files,
+ Inferior, Inferior Thread, Blocks, and Block Iterator APIs now
+ have an is_valid method.
+
** Breakpoints can now be sub-classed in Python, and in particular
you may implement a 'stop' function that is executed each time
the inferior reaches that breakpoint.
libthread_db library with the "set libthread-db-search-path"
command. See the user manual for more details on this command.
+* When natively debugging programs on PowerPC BookE processors running
+ a Linux kernel version 2.6.34 or later, GDB supports ranged breakpoints,
+ which stop execution of the inferior whenever it executes an instruction
+ at any address within the specified range. See the "PowerPC Embedded"
+ section in the user manual for more details.
+
* New features in the GDB remote stub, GDBserver
** GDBserver is now supported on PowerPC LynxOS (versions 4.x and 5.x),
** The --map-info flag lists all known core mappings.
+ ** CFI flashes may be simulated via the "cfi" device.
+
*** Changes in GDB 7.2
* Shared library support for remote targets by default