From: David Bremner <david@tethera.net>
To: rey-coyrehourcq <sebastien.rey-coyrehourcq@univ-rouen.fr>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: Segfault on notmuch compiled using commit 73cebe6e7233f59ba26d9f7c05265b7776795818
Date: Tue, 28 May 2019 07:48:11 -0300 [thread overview]
Message-ID: <87a7f6vor8.fsf@tethera.net> (raw)
In-Reply-To: <1f419873dad2f3034ba709dc58cd958d99b01f44.camel@univ-rouen.fr>
rey-coyrehourcq <sebastien.rey-coyrehourcq@univ-rouen.fr> writes:
> Hi,
> Using Ubuntu 18, i have a segfault after update and recompilation of notmuch at
> commit 73cebe6e7233f59ba26d9f7c05265b7776795818 (HEAD -> master, origin/master,
> origin/HEAD)
Are you running 18.04 or 18.10? Travis is currently successfuly running
the notmuch test suite in Ubuntu 18.04, but it involves supplying quite
a few of the dependencies from a PPA.
Does the notmuch test suite pass on your machine? (make test)
- if yes, that suggests something unanticipated about your mail
store. The GMime messages suggest it has something to do with the new
support for gzipped messages. In this case a backtrace using gdb might
help, as would checking for strange things like dangling symlinks.
- if no, then could you please compare the versions of dependencies with
those reported at
https://api.travis-ci.org/v3/job/538163633/log.txt
Search for "After this operation, 40.7 MB of additional disk space will
be used." to skip some noise at the top.
The version of GMime is particularly important.
d
next prev parent reply other threads:[~2019-05-28 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 8:50 Segfault on notmuch compiled using commit 73cebe6e7233f59ba26d9f7c05265b7776795818 rey-coyrehourcq
2019-05-28 10:48 ` David Bremner [this message]
2019-05-28 12:45 ` sebastien rey-coyrehourcq
2019-05-28 12:59 ` David Bremner
2019-05-28 14:02 ` rey-coyrehourcq
2019-05-29 11:45 ` David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7f6vor8.fsf@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=sebastien.rey-coyrehourcq@univ-rouen.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).