Opened 5 weeks ago
Closed 4 weeks ago
New major version.
GDB 11.1 includes the following changes and enhancements:
* Support for ARM Symbian (arm*-*-symbianelf*) has been removed.
* Building GDB now requires GMP (The GNU Multiple Precision Arithmetic
* New command-line options "--early-init-command" (or "-eix")
and "--early-init-eval-command" (or "-eiex")
* GDB/MI Changes:
** New --qualified option for the '-break-insert' and '-dprintf-insert'
** New --force-condition option for the '-break-insert' and
** New --force option for the '-break-condition' command.
** The '-file-list-exec-source-files' now accepts an optional regular
expression to filter the source files included in the result.
** The results from '-file-list-exec-source-files' now include
a 'debug-fully-read' field to indicate if the corresponding
source's debugging information has been partially read (false)
or has been fully read (true).
* TUI Improvements:
** Mouse actions are now supported. The mouse wheel scrolls
the appropriate window.
** Key combinations that do not have a specific action on the
focused window are now passed to GDB.
* Python enhancements:
** Inferior objects now contain a read-only 'connection_num' attribute that
gives the connection number as seen in 'info connections' and
** New method gdb.Frame.level() which returns the stack level of the
** New method gdb.PendingFrame.level() which returns the stack level
of the frame object.
** When hitting a catchpoint, the Python API will now emit a
gdb.BreakpointEvent rather than a gdb.StopEvent. The
gdb.Breakpoint attached to the event will have type BP_CATCHPOINT.
** Python TUI windows can now receive mouse click events. If the
Window object implements the click method, it is called for each
mouse click event in this window.
** New setting "python ignore-environment on|off"; if "on", causes
GDB's builtin Python to ignore any environment variable that would
otherwise affect how Python behaves (needs to be set during
"early initialization" (see above).
** New setting "python dont-write-bytecode auto|on|off".
* Guile API enhancements:
** Improved support for rvalue reference values.
** New procedures for obtaining value variants:
value-reference-value, value-rvalue-reference-value and
* New "qMemTags" and "QMemTags" remote protocol packets
(associated with Memory Tagging).
* GDB will now look for the .gdbinit file in a config directory before
looking for ~/.gdbinit. The file is searched for in the following
locations: $XDG_CONFIG_HOME/gdb/gdbinit, $HOME/.config/gdb/gdbinit,
$HOME/.gdbinit. On Apple hosts the search order is instead:
* The "break [...] if CONDITION" command no longer returns an error
when the condition is invalid at one or more locations. Instead,
if the condition is valid at one or more locations, the locations
where the condition is not valid are disabled.
The behavior of the "condition" command is changed to match
the new behavior of the "break" command.
* Support for general memory tagging functionality (currently limited
to AArch64 MTE)
* Core file debugging now supported for x86_64 Cygwin programs.
* New "org.gnu.gdb.riscv.vector" feature for RISC-V targets.
* GDB now supports fixed point types which are described in DWARF
as base types with a fixed-point encoding. Additionally, support
for the DW_AT_GNU_numerator and DW_AT_GNU_denominator has also
** New "startup-quietly on|off" setting; when "on", behaves the same
as passing the "-silent" option on the command line.
** New "print type hex on|off" setting; when 'on', the 'ptype' command
uses hexadecimal notation to print sizes and offsets of struct
members. When 'off', decimal notation is used.
** The "inferior" command, when run without argument, prints
information about the current inferior.
** The "ptype" command now supports "/x" and "/d", affecting the base
used to print sizes and offsets.
** The output of the "info source" has been restructured.
** New "style version foreground | background | intensity" commands
to control the styling of the GDB version number.
** Various debug and maintenance commands (mostly useful for
the GDB developers)
1794 unexpected failures in tests, investigating. Majority seem to come from gdb.fortran tests (1368). Next comes "compile-cplus" tests (236)
Fixed at 54bd123605144661a02503a47dd2351195363989
Powered by Trac 1.5.3.dev0
By Edgewall Software
© 1998-2021 Gerard Beekmans.