On Mon 18/10/2021 23:48, Theo Buehler wrote: > +Cc maintainer > > On Mon, Oct 18, 2021 at 09:07:07PM +0000, 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? > > > Thread 1 received signal SIGSEGV, Segmentation fault. > > _libc_freeaddrinfo (ai=0x0) at /usr/src/lib/libc/net/freeaddrinfo.c:46 > > 46 free(p->ai_canonname); > > (gdb) bt > > #0 _libc_freeaddrinfo (ai=0x0) at /usr/src/lib/libc/net/freeaddrinfo.c:46 > > #1 0x0000079ac809e2b6 in getdnsdomainname () > > freeaddrinfo(3) is not NULL safe. > > > 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.falsifian.org 7.0 GENERIC.MP#43 amd64 > > These two kernel lines don't match and don't immediately tell me if > you're on release or -current. 'sysctl kern.version' is better.
I'm reading your mail just after committing a similar diff: I sent this diff yesterday afternoon, offlist, to sthen@ who Ok'ed it. I did not commit earlier because of other things. However, I did manage to open a PR upstream [0]. Hope I did not ruin your plans? https://github.com/neomutt/neomutt/pull/3077
