python2.6 crashed with SIGSEGV in memmove()

Bug #397186 reported by Markus Korn
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zeitgeist (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: python2.6

This python segfault happens reproducible when running lp:zeitgeist-filesystem
I'm not sure what exactly goes wrong, will try to debug it over the weekend.

Note: this filesystem is NOT using python-fuse binding for FUSE, but fusepy from http://code.google.com/p/fusepy/

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Dependencies:
 libgcc1 1:4.3.3-5ubuntu4
 zlib1g 1:1.2.3.3.dfsg-12ubuntu2
 gcc-4.3-base 4.3.3-5ubuntu4
 findutils 4.4.0-2ubuntu4
 libc6 2.9-4ubuntu6
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: python2.6-minimal 2.6.2-0ubuntu1
ProcCmdline: /usr/bin/python bin/zeitgeistfs /home/username/Desktop/zeitgeist
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=de_DE.UTF-8
Signal: 11
SourcePackage: python2.6
StacktraceTop:
 ?? () from /lib/libc.so.6
 memmove () from /lib/libc.so.6
 ffi_call_unix64 ()
 ffi_call ()
 _CallProc ()
Title: python2.6 crashed with SIGSEGV in memmove()
Uname: Linux 2.6.28-13-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Revision history for this message
Markus Korn (thekorn) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:_wordcopy_fwd_aligned (dstp=<value optimized out>,
*__GI_memmove (dest=0x7f977003ad40,
ffi_call_unix64 ()
ffi_call ()
_CallProc ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in python2.6 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Matthias Klose (doko)
affects: python2.6 (Ubuntu) → zeitgeist (Ubuntu)
visibility: private → public
Revision history for this message
Sense Egbert Hofstede (sense) wrote :

Thank you for helping making Ubuntu and Zeitgeist better by reporting this bug. However, before we can pass this on to the developers we need some more information.

You said you can reproduce this bug when using lp:zeitgeist-filesystem. If this is a bug in the development branch rather than the version available from the repositories, you should report this bug against the project Zeitgeist, <https://launchpad.net/zeitgeist>, because this bug is Invalid for Ubuntu.

Zeitgeist is still under heavy development and subject to rapid changes. Maybe this bug has already been fixed. Can you still reproduce it with the latest version of Zeitgeist available from the repositories?

Changed in zeitgeist (Ubuntu):
status: New → Incomplete
Revision history for this message
Sense Egbert Hofstede (sense) wrote :

I'm marking this bug as Invalid because there was no response for one month after I asked and the bug was reported more than five months ago. I'm assuming this is already fixed by now.
However, if you do stumble on this bug again and are willing to provide more information, please don't hesitate to reopen the bug.
Thanks!

Changed in zeitgeist (Ubuntu):
status: Incomplete → Invalid
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.