File _patchinfo of Package patchinfo.21950

Overview Repositories Revisions Requests Users Attributes Meta

File _patchinfo of Package patchinfo.21950

<patchinfo incident="21950">
  <issue tracker="bnc" id="1184214">gdb cannot activate thread debugging using libthread_db</issue>
  <issue tracker="bnc" id="1187044">error reading variable: dwarf2_find_location_expression: Corrupted DWARF expression.</issue>
  <issue tracker="bnc" id="1186040">gdb crash internal-error: jit_event_handler</issue>
  <issue tracker="bnc" id="1180786">gdb license was accidentally changed to SUSE-Public-Domain</issue>
  <issue tracker="bnc" id="1185638">gdb: debugging guix (and maybe other programs?) results in 100% CPU loop in gdb</issue>
  <issue tracker="jsc" id="SLE-19618"/>
  <issue tracker="jsc" id="SLE-19619"/>
  <issue tracker="jsc" id="SLE-19620"/>
  <packager>tomdevries</packager>
  <rating>moderate</rating>
  <category>recommended</category>
  <summary>Recommended update for gdb</summary>
  <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.

</description>
</patchinfo>

Places

File _patchinfo of Package patchinfo.21950

Places