Feedback-ID: i1d2440d7:Fastmail
Date: Mon, 6 Apr 2026 09:32:38 +0200
From: "Peter P." <peterparker@fastmail.com>
To: David Bremner <david@tethera.net>
Subject: Re: Notmuch new: Aborted/Segfault
Message-ID: <7jtfihz3snzdmgxuhh6zpxcrdr4dus6tul6facna5x7vdzjy5o@hklqtqodosr2>
References: <dnnuoy4ncy46ggijxdgdjtho6ajm43ozmjg3ssf4ccqnff5wo4@zujh4y3sx3wh>
 <87cy0c901t.fsf@tethera.net>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <87cy0c901t.fsf@tethera.net>
Message-ID-Hash: 5MGBGSOIOJHQPFNQIRVTPIRA63AQLPP7
CC: notmuch@notmuchmail.org
Precedence: list
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Dear David,
dear list,

thanks for your kind and helpful reply and suggestions. I am a bit
embarassed to say that the error just disappeared this morning after
resuming my laptop from suspending. I will report back here if the error
returns, but for now please consider this as solved/obsolete.

Thanks again,
best, P

* David Bremner <david@tethera.net> [2026-04-06 06:37]:
> "Peter P." <peterparker@fastmail.com> writes:
> 
> > Hi list,
> >
> > (please CC me in your replies, as I am not subscribed to this list)
> >
> > I am getting errors and "Aborted" messages upon running
> > 	notmuch new
> > on a working installation since a few days. The error is
> > 	double free or corruption (out)
> > 	Aborted
> > or with --verbose it's a simple
> > 	Segmentation fault
> 
> You can also try notmuch new --debug, which might give us a bit more
> information.
> 
> >
> > Here is the backtrace:
> >
> > (gdb) double free or corruption (out)
> > Program received signal SIGABRT, Aborted.
> > 0x00007ffff7b8195c in ?? () from /lib/x86_64-linux-gnu/libc.so.6
> > (gdb) bt
> > #0  0x00007ffff7b8195c in ?? () from /lib/x86_64-linux-gnu/libc.so.6
> 
> Can you try with notmuch-dbgsym and libnotmuch5t64-dbgsym installed? You
> will need to add apt sources
> 
> deb http://deb.debian.org/debian-debug/ stable-debug main
> deb http://deb.debian.org/debian-debug/ proposed-updates-debug main
> 
> (the second is probably optional).
> 
> If the segmentation fault happens relatively quickly, it may be
> worthwhile running notmuch under valgrind
> > I have tried re-creating the entire database but without success. What
> > could I try next? This is notmuch 0.39 on a Debian stable system.
> >
> 
> If recreating the database didn't work, it would be good to eliminate
> file system corruption (with fsck) and hardware problems (with
> smartctl).
> 
> Another thing to try is notmuch 0.40-1~bpo13+1 from stable backports.
> 
> Out of curiousity, is there anything exotic about the filesystem?
> 
> d
_______________________________________________
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-leave@notmuchmail.org