SRU: Update gdb to the final 12.1 release in 22.04 LTS

[Matthias Klose]

Update gdb to the final 12.1 release in 22.04 LTS. jammy ships with the gdb 12.1 release candidate, taken from the gdb-12 branch. Changes up to the final release are:

 - updated gnulib library
 - Fix for PR mi/29002 (Windows only)
 - gdb: fix 'remote show FOO-packet' aliases
 - various testsuite fixes
 - fixing compiler warnings
 - Fix bug in Ada number lexing
 - Remove "Ada Settings" node from the manual
 - Handle TLS variable lookups when using separate debug files.
 - PR 28980: gdb: don't copy entirely optimized out values in value_copy
 - gdb/mi: fix use after free of frame_info causing spurious notifications

Comparing the test results between the two builds doesn't show any regression on any architecture.

Also tested with a test rebuild of main, see LP: #1970233.

[Andrea (mariofutire86)]

And it fixes a VSCode integration issue.

https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971409

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Łukasz Zemczak (sil2100)]

Hello Matthias, or anyone else affected,

Accepted gdb into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdb/12.1-0ubuntu1~22.04 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Łukasz Zemczak (sil2100)]

As part of the verification, please perform some general dogfooding of the gdb package from focal-proposed (trying it out in a few random debugging scenarios). Thanks!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted gdb (12.1-0ubuntu1~22.04) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.20.11-0ubuntu82.1 (amd64)
rustc/1.59.0+dfsg1-1~ubuntu2~22.04.1 (arm64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#gdb

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Matthias Klose (doko)]

tested together with the binutils and GCC SRUs. No regressions.

[Kevin Puetz (puetzk)]

> And it fixes a VSCode integration issue.

Also Qt Creator. And probably most any other gdb GUI that displays a "locals" window and therefore might try to display an optimized-out symbol.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gdb - 12.1-0ubuntu1~22.04

---------------
gdb (12.1-0ubuntu1~22.04) jammy-proposed; urgency=medium

  * SRU: LP: #1971474: Update to the final 12.1 release in 22.04 LTS.

 -- Matthias Klose <email address hidden> Tue, 03 May 2022 19:36:23 +0200

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for gdb has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.