offlineimap crashed with SIGSEGV in PyEval_EvalFrameEx()

Bug #545735 reported by Paul Natsuo Kishimoto
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
offlineimap (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: offlineimap

OfflineIMAP is configured to run via a cron job:

*/6 * * * * /usr/bin/offlineimap

With configuration in ~/.offlineimaprc:

[general]
accounts = DreamHost
ui = Noninteractive.Basic

[Account DreamHost]
localrepository = Local
remoterepository = paul-kishimoto-name

[Repository Local]
type = Maildir
localfolders = ~/.local/share/offlineimap/Maildir
sep = /

[Repository paul-kishimoto-name]
type = IMAP
ssl = yes
remotehost = blah.blah.blah.mail.dreamhost.com
remoteuser = [...]
remotepass = [...]
maxconnections = 3
folderfilter = lambda foldername: foldername not in ['INBOX.Trash']

...the apport crash notification shows upon login.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Mar 24 01:06:07 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/offlineimap
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Beta i386 (20100318)
InterpreterPath: /usr/bin/python2.6
Package: offlineimap 6.2.0+nmu2ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/offlineimap
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/sh
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
SegvAnalysis:
 Segfault happened at: 0x80dcd86 <PyEval_EvalFrameEx+1414>: mov 0x2c(%ebx),%eax
 PC (0x080dcd86) ok
 source "0x2c(%ebx)" (0x0000002c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: offlineimap
StacktraceTop:
 PyEval_EvalFrameEx ()
 PyEval_EvalFrameEx ()
 PyEval_EvalCodeEx ()
 ?? ()
 PyObject_Call ()
Title: offlineimap crashed with SIGSEGV in PyEval_EvalFrameEx()
Uname: Linux 2.6.32-17-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Paul Natsuo Kishimoto (khaeru) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 PyEval_EvalFrameEx (f=0x8ddef64, throwflag=0)
 PyEval_EvalFrameEx (f=0x8ddbde4, throwflag=0)
 PyEval_EvalCodeEx (co=0x8ca60b0, globals=0x8ca04f4,
 function_call (func=0x8cb533c, arg=0x8d50c2c, kw=0x8e75acc)
 PyObject_Call (func=0x8cb533c, arg=0x8d50c2c, kw=0x8e75acc)

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 offlineimap (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
dino99 (9d9) wrote :

This version has expired long ago; no more supported

Changed in offlineimap (Ubuntu):
status: New → 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.