Tomboy.exe crashed with SIGSEGV in __memmove_ssse3()

Bug #929057 reported by Muelli
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tomboy (Ubuntu)
New
Undecided
Unassigned

Bug Description

I guess syncing is the issue causing this crash

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: tomboy 1.8.0-1ubuntu1.1.1
ProcVersionSignature: Ubuntu 3.0.0-15.25-generic 3.0.13
Uname: Linux 3.0.0-15-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Wed Feb 8 19:51:24 2012
ExecutablePath: /usr/lib/tomboy/Tomboy.exe
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110201.2)
InterpreterPath: /usr/bin/mono
ProcCmdline: mono /usr/lib/tomboy/Tomboy.exe --search
SegvAnalysis:
 Segfault happened at: 0x7f10c6fcd522 <_IO_vfprintf_internal+50>: mov %eax,-0x518(%rbp)
 PC (0x7f10c6fcd522) ok
 source "%eax" ok
 destination "-0x518(%rbp)" (0x7f10a5c46ea8) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: tomboy
StacktraceTop:
 __memmove_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:119
 g_array_insert_vals () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: Tomboy.exe crashed with SIGSEGV in __memmove_ssse3()
UpgradeStatus: Upgraded to oneiric on 2011-10-17 (114 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Muelli (ubuntu-bugs-auftrags-killer) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #929043, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
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.