All autopkgtests for the newly accepted gdb (8.1.1-0ubuntu1) for bionic have finished running. The following regressions have been reported in tests triggered by the package:
linux-raspi2-5.3/5.3.0-1036.38 (armhf) apport/2.20.9-0ubuntu7.18 (i386) plasma-workspace/unknown (armhf) python3.6/unknown (armhf) python3.7/unknown (armhf, amd64) linux-kvm/unknown (amd64) linux-hwe-5.4/5.4.0-52.57~18.04.1 (armhf) linux-hwe-5.0/unknown (amd64) linux-hwe-5.0/5.0.0-62.67 (armhf) 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/bionic/update_excuses.html#gdb [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1901026 Title: [GDB] No socket file connection support Status in gdb package in Ubuntu: New Status in gdb source package in Bionic: Fix Committed Bug description: GDB on Ubuntu 18.04 (GNU gdb (Ubuntu 8.1-0ubuntu3.2) 8.1.0.20180409-git) does not support connecting to a remote target via a socket file. This is the error we get: (gdb) target remote /run/user/1000/at-spi2-QTZBS0/socket /run/user/1000/at-spi2-QTZBS0/socket: No such device or address. Commit c1168a2f66553cd4730931cf59e3be8378a1a03f enables this in GDB. It would be nice to have it backported. Here's the commit link: https://sourceware.org/git/?p=binutils- gdb.git;a=commit;h=c1168a2f66553cd4730931cf59e3be8378a1a03f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1901026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp