This bug was fixed in the package apport - 2.20.2-0ubuntu1
---
apport (2.20.2-0ubuntu1) yakkety; urgency=medium
[ Brian Murray ]
* data/general-hooks/ubuntu.py: tag bug reports 'apport-hook-error' if they
have an attachment from an apport hook which crashed.
[ Martin Pitt ]
Fixed in http://bazaar.launchpad.net/~apport-
hackers/apport/trunk/revision/3083
** Changed in: apport
Status: New => Fix Released
** Changed in: apport (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Branch linked: lp:apport
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1585702
Title:
not possible to retrace ppc64el crashes
Status in Apport:
Fix Released
Status i
Brian, thanks for testing those. Back when I wrote this I had the
impression that gdb sometimes got confused and needed those additional
"set architecture" commands. But if current versions (≥ trusty) don't
need it, so much the better!
--
You received this bug notification because you are a membe
I also tried my special gdb backport and that works well too.
ubuntu@juju-stg-ue-error-tracker-machine-10:/tmp$ apt-cache policy gdb
gdb:
Installed: 7.10-1ubuntu3~14.04.1
Candidate: 7.10-1ubuntu3~14.04.1
Version table:
*** 7.10-1ubuntu3~14.04.1 0
500 http://ppa.launchpad.net/daisy-p
It's probably worth noting I was testing with the following version of
gdb from Trusty:
*** 7.7.1-0ubuntu5~14.04.2 0
500 http://prodstack-zone-1.clouds.archive.ubuntu.com/ubuntu/
trusty-updates/main amd64 Packages
--
You received this bug notification because you are a member of Ubuntu
If you don't want to remove the arch checks this works:
if 'aarch64' in arch:
command += ['--ex', 'set architecture aarch64', '--ex', 'set
gnutarget elf64-littleaarch64']
elif 'ppc64le' in arch:
command += ['--ex', 'set architecture powerpc:comm
7 matches
Mail list logo
