That looks a lot like the -fstack-clash-protection issue we've been
having recently for other packages on armhf.

dpkg 1.22.1ubuntu3 should fix this ( )

The place where I've written the most details about this is
. If you want I can also upload your package to my test PPA.

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.

  armhf autopkgtests fail due to

Status in apport package in Ubuntu:

Bug description:
  autopkgtests are pretty reliably failing[1] on armhf due to the
  following (single) test failure:

  638s =================================== FAILURES 
  638s ________________ TestApportValgrind.test_valgrind_min_installed 
  638s self = <tests.integration.test_apport_valgrind.TestApportValgrind 
  638s     def test_valgrind_min_installed(self):
  638s         """Valgrind is installed and recent enough."""
  638s         cmd = ["valgrind", "-q", "--extra-debuginfo-path=./", "ls"]
  638s         (ret, out, err) = self._call(cmd)
  638s >       self.assertEqual(err, "")
  638s E       AssertionError: "==2474== Invalid write of size 4\n==2474[1064 
chars]= \n" != ''
  638s E       Diff is 1134 characters long. Set self.maxDiff to None to see it.
  638s tests/integration/ AssertionError

  This could be related to valgrind functionality being different on
  armhf, it could also be related to integer sizes internally on armhf.
  I haven't looked too deeply into it.


To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to