neomutt segmentation fault

I upgraded openBSD and updated packages about 6 hours ago and this was the first issue on this release. Version and dmesg follow, debug. I had quit viewing a message, deleted it, and was changing folders. desktop(~)$: egdb neomutt neomutt.core GNU gdb (GDB) 9.2 Copyright (C) 2020 Free Softw

neomutt segmentation fault

OpenBSD 7.0 release debug-neomutt-20210205-notmuch (installed) neomutt-20210205-notmuch (installed) I guess I shouldn't have commented about not having any dumps. desktop(~)$: egdb neomutt neomutt_20211020.core GNU gdb (GDB) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv

Re: neomutt segmentation fault

On Mon 18/10/2021 23:48, Theo Buehler wrote: > +Cc maintainer > > On Mon, Oct 18, 2021 at 09:07:07PM +, James Cook wrote: > > I don't know if this is related to the other recent neomutt segfault > > thread. > > Unlikely. > > > falsifian moth ~ $ pkg_info neomutt > > Information for inst:neom

Re: neomutt segmentation fault

> > falsifian moth ~ $ pkg_info neomutt > > Information for inst:neomutt-20211015 > > So it seems you're running -current, right? Yes. > > falsifian moth ~ $ dmesg|head -n1 > > OpenBSD 7.0 (GENERIC.MP) #232: Thu Sep 30 14:25:29 MDT 2021 > > > > falsifian moth ~ $ uname -a > > OpenBSD moth.falsi

Re: neomutt segmentation fault

+Cc maintainer On Mon, Oct 18, 2021 at 09:07:07PM +, James Cook wrote: > I don't know if this is related to the other recent neomutt segfault > thread. Unlikely. > falsifian moth ~ $ pkg_info neomutt > Information for inst:neomutt-20211015 So it seems you're running -current, right? > Thre

Re: neomutt segmentation fault

Under 6.9 I had submitted several seq fault traces and had even more not submitted. I was experiencing a fault once a day at least. Stuart provided a patch under 6.9 that greatly reduced the dumps. I had I think two with the patch. With the new version of neomutt (20210205) using 7.0 release

neomutt segmentation fault

I don't know if this is related to the other recent neomutt segfault thread. After sysupgrade -s and pkg_add -u, neomutt crashes immediately when I start it. Is anyone else seeing this? Details below. I took filesystem backups before upgrading, so I can probably figure out the exact (working) neom

Re: neomutt segmentation fault

On Thu, Oct 07, 2021 at 01:31:29PM +0100, Stuart Henderson wrote: On 2021/10/06 21:14, Jon Fineman wrote: Not sure I built this correctly. I applied the patch, ran make in ./mail/neomutt under my userid, then with doas after pkg_add issued errors. I did not run make install. Is it valid to ru

Re: neomutt segmentation fault

On 2021/10/06 21:14, Jon Fineman wrote: > Not sure I built this correctly. I applied the patch, ran make in > ./mail/neomutt under my userid, then with doas after pkg_add issued errors. > I did not run make install. > > Is it valid to run neomutt out of the pobj directory? While it launched and >

Re: neomutt segmentation fault

On Wed, Oct 06, 2021 at 09:14:47PM -0400, Jon Fineman wrote: Not sure I built this correctly. I applied the patch, ran make in ./mail/neomutt under my userid, then with doas after pkg_add issued errors. I did not run make install. Is it valid to run neomutt out of the pobj directory? While i

Re: neomutt segmentation fault

Not sure I built this correctly. I applied the patch, ran make in ./mail/neomutt under my userid, then with doas after pkg_add issued errors. I did not run make install. Is it valid to run neomutt out of the pobj directory? While it launched and I was able to interact with it I did get the bel

Re: neomutt segmentation fault

On 2021/10/04 19:47, Stuart Henderson wrote: > On 2021/10/04 09:22, Jon Fineman wrote: > > I had been using it about 5 minutes and just entered a few commands. > > Hopefully one of these will help. dmesg follows. It is rather random with > > staying up days to just a few minutes. > > It probably n

Re: neomutt segmentation fault

On 2021/10/04 09:22, Jon Fineman wrote: > I had been using it about 5 minutes and just entered a few commands. > Hopefully one of these will help. dmesg follows. It is rather random with > staying up days to just a few minutes. It probably needs reporting upstream, but there's a new release of neo

neomutt segmentation fault

I had been using it about 5 minutes and just entered a few commands. Hopefully one of these will help. dmesg follows. It is rather random with staying up days to just a few minutes. desktop(~)$: egdb neomutt neomutt.core GNU gdb (GDB) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. L

neomutt Segmentation fault (core dumped)

I had only been using neomutt about 10 minutes. desktop(~)$: uname -a OpenBSD desktop 6.9 GENERIC.MP#4 amd64 desktop(~)$: desktop(~)$: egdb neomutt neomutt.core GNU gdb (GDB) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

Re: neomutt Segmentation fault (core dumped)

:2061 #11 0x083e13694799 in main (argc=, argv=, envp=) at ../neomutt-20210205/main.c:1238 (gdb) - Original message - From: Stuart Henderson To: Jon Fineman Cc: ports@openbsd.org Subject: Re: neomutt Segmentation fault (core dumped) Date: Saturday, July 10, 2021 7:08 AM On 202

Re: neomutt Segmentation fault (core dumped)

On 2021/07/10 06:44, Jon Fineman wrote: > It had been running for several days. Ran the '$' command to purge messages > marked for deletion. I have the debug package installed, not sure why I am > not getting more info from egdb. > > > desktop(~)$: egdb debug-neomutt-20210205-notmuch neomutt.co

neomutt Segmentation fault (core dumped)

It had been running for several days. Ran the '$' command to purge messages marked for deletion. I have the debug package installed, not sure why I am not getting more info from egdb. desktop(~)$: egdb debug-neomutt-20210205-notmuch neomutt.core GNU gdb (GDB) 7.12.1 Copyright (C) 2017 Free Soft