Crashed during s-i's test_pause during a local test build of s-i

Bug #1351373 reported by Barry Warsaw
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-download-manager (Ubuntu)
New
Medium
Unassigned

Bug Description

I think this crashed when sending a 'pause' signal to u-d-m, but I will try to gather more information.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: ubuntu-download-manager 0.7+14.10.20140725-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ApportVersion: 2.14.5-0ubuntu2
Architecture: amd64
Date: Fri Aug 1 11:54:06 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/ubuntu-download-manager
InstallationDate: Installed on 2011-07-12 (1115 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
ProcCmdline: /usr/bin/ubuntu-download-manager -self-signed-certs /build/system-image-g5L18v/system-image-2.3.2/systemimage/tests/data/cert.pem -disable-timeout -stoppable -log-dir /tmp/tmp7qo6was_
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/sh
 LD_PRELOAD=<set>
 PATH=(custom, no user)
 TERM=xterm
Signal: 6
SourcePackage: ubuntu-download-manager
SystemImageInfo:
 current build number: 0
 device name:
 channel: daily
 last update: Unknown
UpgradeStatus: Upgraded to utopic on 2011-12-23 (951 days ago)
UserGroups: adm admin autopilot cdrom dialout fuse libvirtd lpadmin plugdev sambashare sbuild

Revision history for this message
Barry Warsaw (barry) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 <unavailable> in ?? ()
 PC unavailable, cannot determine locals.
 Backtrace stopped: not enough registers or memory available to unwind further
StacktraceSource: #0 <unavailable> in ?? ()
StacktraceTop: <unavailable> in ?? ()
ThreadStacktrace:
 PC register is not available
 PC register is not available

Changed in ubuntu-download-manager (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Barry Warsaw (barry)
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.