[Bug 2059856] Re: [SRU] gdb 10.0 fails to examine any global variables in D programs

[Timo Aaltonen]

Hello Zixing, 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.3 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.

** Changed in: gdb (Ubuntu Jammy)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/2059856

Title:
  [SRU] gdb 10.0 fails to examine any global variables in D programs

Status in gdb:
  Fix Released
Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Jammy:
  Fix Committed
Status in gdb source package in Noble:
  Fix Released
Status in gdb source package in Oracular:
  Fix Released
Status in gdb source package in Plucky:
  Fix Released

Bug description:
  [Impact]

   * GDB 10.0 introduced a regression where it cannot inspect any global variables in any D programs compiled by any D compiler.
   * LDC2 and GDC upstream stated Focal does not have such a problem and stuck to this release for their test images.

  [Test Plan]

  Considering the following D program:

  ```
  module t;

  class uv {
      int i;
  }

  __gshared uv i;
  int main() {
      i = new uv();
      return 0; // #break
  }
  ```

  If you build it using `gdc -g -O0 t.d -o t` or `ldc2 -o t.o t.d -g`,
  run the GDB using the following commands ...

  ```
  b t.d:10
  p t.i
  ```

  ... you will notice GDB will complain that "'t.i' has unknown type;
  cast it to its declared type."

  [Where problems could occur]

    * The fix consists of a single line change to the demangler. The worst-case scenario would be breaking the demangling functionality of other programming languages. However, the newer D ABI uses a symbol mangling scheme that is very difficult to confuse with other programming languages.
    * Incorrect symbol de-mangling may also cause user confusion. However, the patch fixed a fundamental usability issue.

  [Other Info]

    * Initial discussion in the LDC2 bug tracker:
  https://github.com/ldc-developers/ldc/issues/4389

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2059856/+subscriptions