workrave crashed with SIGSEGV in _int_malloc()

Bug #1187645 reported by Timo Jyrinki
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Unity
Invalid
Undecided
Unassigned
Workrave
New
Undecided
Unassigned

Bug Description

Got the apport dialog after a reboot.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: workrave 1.10-0ubuntu2
ProcVersionSignature: Ubuntu 3.9.0-3.8-generic 3.9.4
Uname: Linux 3.9.0-3-generic x86_64
ApportVersion: 2.10.2-0ubuntu1
Architecture: amd64
CheckboxSubmission: 1896b893828b4203b948b1eb6546be06
CheckboxSystem: d00f84de8a555815fa1c4660280da308
CrashCounter: 1
Date: Wed Jun 5 09:10:05 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/workrave
InstallationDate: Installed on 2012-03-16 (445 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120316)
MarkForUpload: True
ProcCmdline: /usr/bin/workrave
SegvAnalysis:
 Segfault happened at: 0x7f6aaa6492bd <_int_malloc+669>: mov %rbp,0x10(%r11)
 PC (0x7f6aaa6492bd) ok
 source "%rbp" ok
 destination "0x10(%r11)" (0x00000010) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: workrave
StacktraceTop:
 _int_malloc (av=0x7f6aaa989740 <main_arena>, bytes=<optimized out>) at malloc.c:3424
 __GI___libc_malloc (bytes=537) at malloc.c:2859
 operator new(unsigned long) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 std::string::_Rep::_S_create(unsigned long, unsigned long, std::allocator<char> const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 std::string::_Rep::_M_clone(std::allocator<char> const&, unsigned long) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
Title: workrave crashed with SIGSEGV in _int_malloc()
UpgradeStatus: Upgraded to saucy on 2013-06-04 (0 days ago)
UserGroups: adm autopilot cdrom dip lp lpadmin motion plugdev sambashare sudo

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :
Stephen M. Webb (bregma)
Changed in unity:
status: New → Invalid
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.