Hello bugproxy, or anyone else affected, Accepted binutils into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/binutils/2.26.1-1ubuntu1~16.04.7 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: binutils (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1781242 Title: as segfault with invalid -march= option Status in Ubuntu on IBM z Systems: In Progress Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Xenial: Fix Committed Bug description: [Impact] * as segfaults, instead of exiting gracefully, when one specifies unsupported arch option (ie. one from future - cause xenial did not support z14) * this is bad, as detection fails around supported march options - as if binutils are completely broken, rather than just not supporting this or that CPU level of optimisations. [Test Case] Bad result: $ as -march=foo Segmentation fault Expected result: # as -march=foo Assembler messages: Error: invalid switch -march=foo Error: unrecognized option -march=foo [Regression Potential] * The result is still a failure condition, but with a proper exit code and standard error messages, rather than an unexplainable generic segfault. [Other Info] * Original bug report The GNU assembler segfaults with an invalid -march= option Contact Information = n/a ---uname output--- n/a Machine Type = n/a ---Debugger--- A debugger is not configured ---Steps to Reproduce--- $ as -march=foo Segmentation fault Expected result: # as -march=foo Assembler messages: Error: invalid switch -march=foo Error: unrecognized option -march=foo Userspace tool common name: as The userspace tool has the following bit modes: 64 Userspace rpm: binutils-2.26.1-1ubuntu1~16.04.6 Userspace tool obtained from project website: na *Additional Instructions for n/a: -Attach ltrace and strace of userspace application. The problem is not critical since usually 'as' is invoked through the gcc driver which itself errors out for wrong -march= options. It will only be a problem if somebody builds a more recent GCC from source and uses an -march= option for a machine not supported by the default binutils. Please consider integrating the attached patch into 16.04 binutils. The problem has been fixed in later binutils already. Ubuntu 18.04 does not appear to be affected. --> Package has to set corectly by Canonical To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781242/+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
