apport-retrace strangely exits with 0 return code
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Fix Released
|
Undecided
|
Martin Pitt |
Bug Description
apport/
# 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.
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_
Related branches
Changed in apport (Ubuntu): | |
assignee: | nobody → Martin Pitt (pitti) |
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().