neomutt crashed with SIGSEGV in cmd_parse_expunge()

Bug #1853909 reported by Dan Watkins
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neomutt (Ubuntu)
New
Medium
Unassigned

Bug Description

I had copied a bunch of files to a different folder and when I hit $ to expunge my inbox, I hit this crash.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: neomutt 20191111+dfsg.1-1
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
CrashCounter: 1
CurrentDesktop: i3
Date: Mon Nov 25 12:57:16 2019
ExecutablePath: /usr/bin/neomutt
ExecutableTimestamp: 1573627661
InstallationDate: Installed on 2019-05-07 (202 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcCmdline: /usr/bin/neomutt
ProcCwd: /home/daniel
SegvAnalysis:
 Segfault happened at: 0x555555631707 <imap_cmd_step+1319>: subl $0x1,0x8(%rax)
 PC (0x555555631707) ok
 source "$0x1" ok
 destination "0x8(%rax)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: neomutt
StacktraceTop:
 cmd_parse_expunge (adata=0x555555717490, s=<optimized out>) at ../imap/command.c:270
 cmd_handle_untagged (adata=0x555555717490) at ../imap/command.c:997
 imap_cmd_step (adata=<optimized out>) at ../imap/command.c:1130
 imap_cmd_step (adata=0x555555717490) at ../imap/command.c:1071
 imap_exec (cmdstr=0x5555556805d7 "EXPUNGE", flags=<optimized out>, adata=0x555555717490) at ../imap/command.c:1267
Title: neomutt crashed with SIGSEGV in cmd_parse_expunge()
UpgradeStatus: Upgraded to focal on 2019-11-15 (10 days ago)
UserGroups: adm boinc cdrom dip docker libvirt lpadmin lxd plugdev sambashare sbuild sudo
separator:

Revision history for this message
Dan Watkins (oddbloke) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 cmd_parse_expunge (adata=0x555555717490, s=<optimized out>) at ../imap/command.c:270
 cmd_handle_untagged (adata=0x555555717490) at ../imap/command.c:997
 imap_cmd_step (adata=<optimized out>) at ../imap/command.c:1130
 imap_cmd_step (adata=0x555555717490) at ../imap/command.c:1071
 imap_exec (cmdstr=0x5555556805d7 "EXPUNGE", flags=<optimized out>, adata=0x555555717490) at ../imap/command.c:1267

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in neomutt (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Dan Watkins (oddbloke) wrote :

I've reported this upstream as https://github.com/neomutt/neomutt/issues/1993

information type: Private → Public
Revision history for this message
Dan Watkins (oddbloke) wrote :

Still present in 20191207+dfsg.1-1.1.

Revision history for this message
Dan Watkins (oddbloke) wrote :

The upstream issue was closed due to the age of the version I reported with; groovy has a more recent version so I've opened https://github.com/neomutt/neomutt/issues/2549 for this issue.

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.