boincmgr crashed with SIGSEGV

Bug #1202724 reported by Daniel Winzen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
boinc (Ubuntu)
Undecided
Unassigned

Bug Description

My hard disk was writing/reading a lot and my computer was responding really slow, because I had many tabs open in firefox. I stared boincmgr, because I thought it may be related to boinc and then boincmgr crashed. After I closed firefox I restarted the boincmgr and this time it was working.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: boinc-manager 7.1.21+dfsg-1
ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
Uname: Linux 3.10.0-3-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Thu Jul 18 17:27:56 2013
ExecutablePath: /usr/bin/boincmgr
InstallationDate: Installed on 2013-02-27 (141 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130226)
MarkForUpload: True
ProcCmdline: boincmgr
SegvAnalysis:
 Segfault happened at: 0x7f21f3a63008: cmpb $0x48,(%rcx)
 PC (0x7f21f3a63008) ok
 source "$0x48" ok
 destination "(%rcx)" (0xf42bb3f8) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: boinc
StacktraceTop:
 ?? ()
 ?? ()
Title: boincmgr crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Daniel Winzen (q-d-deactivatedaccount) wrote :
information type: Private → Public
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

Can you reproduce the issue realiabily? I don't know how to deal with this issue...

Revision history for this message
Daniel Winzen (q-d-deactivatedaccount) wrote :

No, I can't reproduce it. I had this version already for a long time installed and this was the first and only time it crashed with this error.

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

StacktraceTop:
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in boinc (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for dconf-gsettings-backend: package version 0.16.1-1 dbgsym version 0.16.0-4
outdated debug symbol package for libexpat1: package version 2.1.0-4 dbgsym version 2.1.0-2

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers