SUSE-RU-2021:3890-1: moderate: Recommended update for gdb

Fri Dec 3 14:54:06 UTC 2021

   SUSE Recommended Update: Recommended update for gdb
______________________________________________________________________________

Announcement ID:    SUSE-RU-2021:3890-1
Rating:             moderate
References:         #1180786 #1184214 #1185638 #1186040 #1187044 
                    SLE-19618 SLE-19619 SLE-19620 
Affected Products:
                    SUSE Linux Enterprise Module for Development Tools 15-SP3
                    SUSE Linux Enterprise Module for Development Tools 15-SP2
______________________________________________________________________________

   An update that has 5 recommended fixes and contains three
   features can now be installed.

Description:

   This update for gdb fixes the following issues:

   Rebase to 11.1 release (as in fedora 35 @ 9cd9368):

   * GDB now supports general memory tagging functionality if the underlying
     architecture supports the proper primitives and hooks. Currently this is
     enabled only for AArch64 MTE.
   * 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.
   * GDB will now load and process commands from ~/.config/gdb/gdbearlyinit
     or ~/.gdbearlyinit if these files are present.  These files are
     processed earlier than any of the other initialization files and can
     affect parts of GDB's startup that previously had already been completed
     before the initialization files were read, for example styling of the
     initial GDB greeting.
   * GDB now has two new options "--early-init-command" and
     "--early-init-eval-command" with corresponding short options "-eix" and
     "-eiex" that allow options (that would normally appear in a gdbearlyinit
     file) to be passed on the command line.
   * set startup-quietly on|off show startup-quietly When 'on', this causes
     GDB to act as if "-silent" were passed
     on the command line.  This command needs to be added to an early
      initialization file (e.g. ~/.config/gdb/gdbearlyinit) in order to
      affect GDB.
   * For RISC-V targets, the target feature "org.gnu.gdb.riscv.vector" is now
     understood by GDB, and can be used to describe the vector registers of a
     target.
   * TUI windows now support mouse actions.  The mouse wheel scrolls the
     appropriate window.
   * Key combinations that do not have a specific action on the focused
     window are passed to GDB.  For example, you now can use
     Ctrl-Left/Ctrl-Right to move between words in the command window
     regardless of which window is in focus.  Previously you would need to
     focus on the command window for such key combinations to work.
   * set python ignore-environment on|off show python ignore-environment

     When 'on', this causes GDB's builtin Python to ignore any environment
   variables that would otherwise affect how Python behaves.  This command
   needs to be added to an early initialization file (e.g.
   ~/.config/gdb/gdbearlyinit) in
     order to affect GDB.

   * set python dont-write-bytecode auto|on|off show python
     dont-write-bytecode

     When 'on', this causes GDB's builtin Python to not write any byte-code
   (.pyc files) to disk.  This command needs to be added to an early
   initialization file (e.g. ~/.config/gdb/gdbearlyinit) in order to affect
   GDB. When 'off' byte-code will always be written. When set to 'auto' (the
   default) Python will check the PYTHONDONTWRITEBYTECODE environment
   variable.

   * break [PROBE_MODIFIER] [LOCATION] [thread THREADNUM] [-force-condition]
     [if CONDITION]

     This command would previously refuse setting a breakpoint if the
   CONDITION expression is invalid at a location.  It now accepts and defines
   the breakpoint if there is at least one location at which the CONDITION is
   valid.  The locations for which the CONDITION is invalid, are
   automatically disabled.  If CONDITION is invalid at all of the locations,
   setting the breakpoint is still rejected.  However, the '-force-condition'
   flag can be used in this case for forcing GDB to define the breakpoint,
   making all the current locations automatically disabled.  This may be
   useful if the user knows the condition will become meaningful at a future
   location, e.g. due to a shared library load.
   - Update libipt to v2.0.4.

Patch Instructions:

   To install this SUSE Recommended Update use the SUSE recommended installation methods
   like YaST online_update or "zypper patch".

   Alternatively you can run the command listed for your product:

   - SUSE Linux Enterprise Module for Development Tools 15-SP3:

      zypper in -t patch SUSE-SLE-Module-Development-Tools-15-SP3-2021-3890=1

   - SUSE Linux Enterprise Module for Development Tools 15-SP2:

      zypper in -t patch SUSE-SLE-Module-Development-Tools-15-SP2-2021-3890=1

Package List:

   - SUSE Linux Enterprise Module for Development Tools 15-SP3 (aarch64 ppc64le s390x x86_64):

      gdb-11.1-8.27.1
      gdb-debuginfo-11.1-8.27.1
      gdb-debugsource-11.1-8.27.1
      gdbserver-11.1-8.27.1
      gdbserver-debuginfo-11.1-8.27.1

   - SUSE Linux Enterprise Module for Development Tools 15-SP2 (aarch64 ppc64le s390x x86_64):

      gdb-11.1-8.27.1
      gdb-debuginfo-11.1-8.27.1
      gdb-debugsource-11.1-8.27.1
      gdbserver-11.1-8.27.1
      gdbserver-debuginfo-11.1-8.27.1

References:

   https://bugzilla.suse.com/1180786
   https://bugzilla.suse.com/1184214
   https://bugzilla.suse.com/1185638
   https://bugzilla.suse.com/1186040
   https://bugzilla.suse.com/1187044