touch-packages team mailing list archive

[Launchpad Bug Tracker <1354571@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package apport - 2.14.7-0ubuntu1

---------------
apport (2.14.7-0ubuntu1) utopic; urgency=medium

  * New upstream release:
    - Fix interpretation of core dump ulimits: they are in bytes, not KiB.
      (LP: #1346497)
    - apport-retrace: Don't require specifying an operation; default to
      updating the given .crash file. (LP: #1361242)
    - Write report even on UnreportableReasons, so that whoopsie can still
      upload them. (LP: #1360417)
    - apt/dpkg install_packages(): Write a "packages.txt" into sandbox root
      directory to keep track of installed packages and their versions.
      Prerequisite for LP #1352591.
    - apt/dpkg install_packages(): Avoid re-downloading/installing packages
      which are already installed into a permanent sandbox. Prerequisite for
      LP #1352591.
    - sandboxutils.py, make_sandbox(): Drop check for already existing files
      when dynamically resolving libraries and ExecutablePaths; with that,
      these packages would never get updated in a permanent sandbox. The new
      version tracking from above now takes care of that. (LP: #1352591)
    - Fix report.test_add_proc_info test to stop assuming that pid 1 is named
      "init", as one can specify a different one on the kernel command line.
    - report.py, add_gdb_info(): Check for truncated core dumps, and set
      UnreportableReason and raise an IOError on them. Handle this in
      apport-retrace and whoopsie-upload-all to fail properly instead of
      silently producing broken Stacktraces. (LP: #1354571)
 -- Martin Pitt <martin.pitt@xxxxxxxxxx>   Fri, 29 Aug 2014 12:38:54 +0200

** Changed in: apport (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
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:
  Fix Released

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