Here is the log file from the Error Tracker retracer trying to retrace the crash:
e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08 11:21:45,422:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:Processing. e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08 11:21:45,447:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:swift token: de4d505d664547f086a4ee328ba87631 e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08 11:21:45,575:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:Decompressing to /tmp/tmpxKHbHR-swift.f158f61e-1eec-11e4-9491-fa163e75317b.oopsid.core e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08 11:21:45,887:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:Retracing f158f61e-1eec-11e4-9491-fa163e75317b:swift e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08 11:22:02,312:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:Writing back to Cassandra e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08 11:22:02,344:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:Apport did not return a crash_signature. e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08 11:22:02,345:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:StacktraceTop: e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08 11:22:02,345:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:?? () e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08 11:22:02,345:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:?? () e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08 11:22:02,346:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:Could not retrace. e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08 11:22:03,108:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:Done processing /tmp/tmpxKHbHR-swift.f158f61e-1eec-11e4-9491-fa163e75317b.oopsid e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08 11:22:03,108:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:swift token: de4d505d664547f086a4ee328ba87631 -- 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/1354571 Title: apport-retrace ignores warnings from gdb Status in “apport” package in Ubuntu: New Bug description: I was trying to investigate a failed retrace on armhf and received the following when running apport-retrace with -g. Calling gdb command: gdb-multiarch --ex 'set architecture arm' --ex 'set gnutarget elf32-littlearm' --ex 'set debug-file-directory /tmp/apport -utopic/usr/lib/debug' --ex 'set solib-absolute-prefix /tmp/apport-utopic' --ex 'file "/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing- helper"' --ex 'core-file /tmp/apport_core_36z3Va' GNU gdb (Ubuntu 7.7-0ubuntu3.2) 7.7 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". The target architecture is assumed to be arm Reading symbols from /tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-helper...Reading symbols from /tmp/apport-utopic/usr/lib/debug/.bu ild-id/0d/28e75c6b9149132f8940077618a904989a75ed.debug...done. done. BFD: Warning: /tmp/apport_core_36z3Va is truncated: expected core file size >= 19316736, found: 9502720. [New LWP 15327] [New LWP 15530] [New LWP 15321] Cannot access memory at address 0xb6fa7948 Cannot access memory at address 0xb6fa7944 When running apport-retrace with -o, a new crash file is created with a broken Stacktrace. This makes sense given that the core file is corrupt. However, I think apport-retrace should do something different here, as you have no idea why the retraced report is bad. Maybe it should write a RetraceFailure key to the report, not write the report at all, or just exit with an error regarding the core file size difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1354571/+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
