mutt-org crashed with SIGSEGV

Bug #666286 reported by Matt Zimmerman
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mutt (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: mutt

This crash happened while in the index view, reading email over IMAP

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: mutt 1.5.20-9ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Mon Oct 25 09:44:44 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/mutt-org
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Alpha i386 (20100315)
ProcCmdline: mutt
ProcEnviron:
 PATH=(custom, user)
 SHELL=/bin/zsh
 LANG=en_US.UTF-8
 LC_COLLATE=C
SegvAnalysis:
 Segfault happened at: 0x80f07a5: cmpb $0x4,0x4(%ebx)
 PC (0x080f07a5) ok
 source "$0x4" ok
 destination "0x4(%ebx)" (0x00000014) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: mutt
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: mutt-org crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

StacktraceTop:
 imap_check_mailbox (ctx=0x8905748, index_hint=0x0, force=1)
 imap_keepalive () at ../../imap/util.c:761
 km_dokey (menu=6) at ../keymap.c:396
 mutt_index_menu () at ../curs_main.c:623
 main (argc=1, argv=0xbffa5444) at ../main.c:1026

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

This version has expired long time ago, and is no more supported

Changed in mutt (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.