touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Indeed, thanks for spotting! Fixed in http://bazaar.launchpad.net
/~apport-hackers/apport/trunk/revision/2968 , this also cleaned up a few
other errors to consistently use apport.fatal().

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

-- 
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/1462469

Title:
  apport-retrace strangely exits with 0 return code

Status in apport package in Ubuntu:
  Fix Committed

Bug description:
  apport/sandboxutils.py contains the following code:

      # sanity check: for a packaged binary we require having the executable in
      # the sandbox; TODO: for an unpackage binary we don't currently copy its
      # potential local library dependencies (like those in build trees) into the
      # sandbox, and we call gdb/valgrind on the binary outside the sandbox.
      if 'Package' in report:
          for path in ('InterpreterPath', 'ExecutablePath'):
              if path in report and not os.path.exists(sandbox_dir + report[path]):
                  apport.error('%s %s does not exist (report specified package %s)',
                               path, sandbox_dir + report[path], report['Package'])
                  sys.exit(0)

  I don't think apport should exit with a 0 here, as setting up the
  sandbox and the retrace was not successful. I discovered this when
  trying to retrace _usr_lib_checkbox_qt_checkbox-qt-service.2001.crash
  which is part of apport-test crashes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1462469/+subscriptions