Hello Brian, or anyone else affected, Accepted gdb into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdb/7.11.90.20161005-0ubuntu2 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, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gdb (Ubuntu Yakkety) Status: Triaged => Fix Committed ** Tags added: verification-needed -- 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/1645501 Title: corefiles not created in armhf chroot on arm64 porter Status in gdb package in Ubuntu: Fix Released Status in gdb source package in Precise: Invalid Status in gdb source package in Trusty: Triaged Status in gdb source package in Xenial: Triaged Status in gdb source package in Yakkety: Fix Committed Bug description: Impact ------ Its not possible to create a corefile in an armhf chroot on an arm64 system. Test Case --------- On an arm64 system enter an armhf chroot, then 1) execute "gdb --args cat" 2) in gdb type run 3) press Ctrl-Z 4) generate-core-file /tmp/my.core With the current version of gdb you'll see "Unable to fetch floating point registers.", with the version in -proposed you'll see "Saved corefile". Regression Potential -------------------- The corefiles aren't created at all in this scenario so things should improve. I'm filing this about gdb per Steve's suggestion, although this could be an issue somewhere else. I recently discovered that the apport-test-crash (https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment /test-crashes) crash files produced for armhf are crash files without CoreDumps. This happened sometime between 20160531 and 20161025. I've recreated this on the porter-arm64 box with the following minimal test case (generate-sigsegv-crash.py is from apport-test-crashes): schroot -c yakkety-armhf python generate-sigsegv-crash.py cat Running this on both armhf and arm64 we can see the following different output. armhf chroot on porter-armhf: 47 Program received signal SIGSEGV, Segmentation fault. 48 0xb6f599e4 in read () at ../sysdeps/unix/syscall-template.S:84 49 84 ../sysdeps/unix/syscall-template.S: No such file or directory. 50 (gdb) Saved corefile /tmp/tmp840s08i1/my.core armhf chroot on porter-arm64: 47 Program received signal SIGSEGV, Segmentation fault. 48 0xf772f9e4 in read () at ../sysdeps/unix/syscall-template.S:84 49 84 ../sysdeps/unix/syscall-template.S: No such file or directory. 50 (gdb) Unable to fetch the floating point registers.: Invalid argument. Notice how there is no core file save on porter-arm64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1645501/+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
