* Segfault in libxapian when searching
@ 2019-10-29 17:50 Sebastian Poeplau
2019-10-29 17:57 ` Sebastian Poeplau
0 siblings, 1 reply; 3+ messages in thread
From: Sebastian Poeplau @ 2019-10-29 17:50 UTC (permalink / raw)
To: notmuch
Hi all,
After a recent upgrade to Notmuch 0.29.2 and Xapian 1.4.13 I see Notmuch
fail with a segmentation fault inside libxapian.so when executing
queries that I've been running regularly and without problems before.
Let me start with the stack trace:
Stack trace of thread 3133:
#0 0x00007fe0eb4ecee4 n/a (libxapian.so.30)
#1 0x00007fe0eb4f06fe n/a (libxapian.so.30)
#2 0x00007fe0eb4f7284 n/a (libxapian.so.30)
#3 0x00007fe0eb4161f8 _ZNK6Xapian7Enquire8Internal8get_msetEjjjPKNS_4RSetEPKNS_12MatchDeciderE (libxapian.so.30)
#4 0x00007fe0eb416466 _ZNK6Xapian7Enquire8get_msetEjjjPKNS_4RSetEPKNS_12MatchDeciderE (libxapian.so.30)
#5 0x00007fe0ebbc49ca n/a (libnotmuch.so.5)
#6 0x00007fe0ebbc527e notmuch_query_search_threads (libnotmuch.so.5)
#7 0x0000557fc9f05c68 n/a (notmuch)
#8 0x0000557fc9efa12c n/a (notmuch)
#9 0x00007fe0eb5d7153 __libc_start_main (libc.so.6)
#10 0x0000557fc9efa2ee n/a (notmuch)
The type of query in question is the following: "not tag:notmuch-list
and to:notmuch@notmuchmail.org". It crashes, but only if there is a
matching message. Quoting the email address separately doesn't change
anything. I have several such queries for different lists in my post-new
hook, and the problem seems to apply to all of them.
When I run the search with NOTMUCH_DEBUG_QUERY=1, I get the following
query information:
Query string is:
not tag:notmuch-list and to:notmuch@notmuchmail.org
Exclude query is:
Query((Kdeleted OR Kspam))
Final query is:
Query(((Tmail AND ((<alldocuments> AND_NOT Knotmuch-list) AND (XTOnotmuch@1 PHRASE 3 XTOnotmuchmail@2 PHRASE 3 XTOorg@3))) AND_NOT (Kdeleted OR Kspam)))
Does anyone have an idea where the problem could be or how to
investigate further?
Thanks,
Sebastian
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Segfault in libxapian when searching
2019-10-29 17:50 Segfault in libxapian when searching Sebastian Poeplau
@ 2019-10-29 17:57 ` Sebastian Poeplau
2019-10-29 18:22 ` Sebastian Poeplau
0 siblings, 1 reply; 3+ messages in thread
From: Sebastian Poeplau @ 2019-10-29 17:57 UTC (permalink / raw)
To: notmuch
Sorry, I just discovered that the problem has been reported before for
the Arch package "xapian-core" [0] and upstream with the Xapian project
[1]. It seems to be a bug on their side that should be fixed in the next
release.
Anyway, if anyone runs into the same issue they can now find the
references on this list also ;)
Cheers,
Sebastian
[0] https://bugs.archlinux.org/task/64273?project=1&string=xapian-core
[1] https://trac.xapian.org/ticket/796
Sebastian Poeplau <sebastian.poeplau@eurecom.fr> writes:
> Hi all,
>
> After a recent upgrade to Notmuch 0.29.2 and Xapian 1.4.13 I see Notmuch
> fail with a segmentation fault inside libxapian.so when executing
> queries that I've been running regularly and without problems before.
>
> Let me start with the stack trace:
>
> Stack trace of thread 3133:
> #0 0x00007fe0eb4ecee4 n/a (libxapian.so.30)
> #1 0x00007fe0eb4f06fe n/a (libxapian.so.30)
> #2 0x00007fe0eb4f7284 n/a (libxapian.so.30)
> #3 0x00007fe0eb4161f8 _ZNK6Xapian7Enquire8Internal8get_msetEjjjPKNS_4RSetEPKNS_12MatchDeciderE (libxapian.so.30)
> #4 0x00007fe0eb416466 _ZNK6Xapian7Enquire8get_msetEjjjPKNS_4RSetEPKNS_12MatchDeciderE (libxapian.so.30)
> #5 0x00007fe0ebbc49ca n/a (libnotmuch.so.5)
> #6 0x00007fe0ebbc527e notmuch_query_search_threads (libnotmuch.so.5)
> #7 0x0000557fc9f05c68 n/a (notmuch)
> #8 0x0000557fc9efa12c n/a (notmuch)
> #9 0x00007fe0eb5d7153 __libc_start_main (libc.so.6)
> #10 0x0000557fc9efa2ee n/a (notmuch)
>
> The type of query in question is the following: "not tag:notmuch-list
> and to:notmuch@notmuchmail.org". It crashes, but only if there is a
> matching message. Quoting the email address separately doesn't change
> anything. I have several such queries for different lists in my post-new
> hook, and the problem seems to apply to all of them.
>
> When I run the search with NOTMUCH_DEBUG_QUERY=1, I get the following
> query information:
>
> Query string is:
> not tag:notmuch-list and to:notmuch@notmuchmail.org
> Exclude query is:
> Query((Kdeleted OR Kspam))
> Final query is:
> Query(((Tmail AND ((<alldocuments> AND_NOT Knotmuch-list) AND (XTOnotmuch@1 PHRASE 3 XTOnotmuchmail@2 PHRASE 3 XTOorg@3))) AND_NOT (Kdeleted OR Kspam)))
>
> Does anyone have an idea where the problem could be or how to
> investigate further?
>
> Thanks,
> Sebastian
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Segfault in libxapian when searching
2019-10-29 17:57 ` Sebastian Poeplau
@ 2019-10-29 18:22 ` Sebastian Poeplau
0 siblings, 0 replies; 3+ messages in thread
From: Sebastian Poeplau @ 2019-10-29 18:22 UTC (permalink / raw)
To: notmuch
Now that my setup works again, I see that others have already mentioned
the issue even on this list. Ironically, I hadn't seen those messages
before because the bug broke my tagging of list messages...
Sebastian Poeplau <sebastian.poeplau@eurecom.fr> writes:
> Sorry, I just discovered that the problem has been reported before for
> the Arch package "xapian-core" [0] and upstream with the Xapian project
> [1]. It seems to be a bug on their side that should be fixed in the next
> release.
>
> Anyway, if anyone runs into the same issue they can now find the
> references on this list also ;)
>
> Cheers,
> Sebastian
>
> [0] https://bugs.archlinux.org/task/64273?project=1&string=xapian-core
> [1] https://trac.xapian.org/ticket/796
>
>
> Sebastian Poeplau <sebastian.poeplau@eurecom.fr> writes:
>
>> Hi all,
>>
>> After a recent upgrade to Notmuch 0.29.2 and Xapian 1.4.13 I see Notmuch
>> fail with a segmentation fault inside libxapian.so when executing
>> queries that I've been running regularly and without problems before.
>>
>> Let me start with the stack trace:
>>
>> Stack trace of thread 3133:
>> #0 0x00007fe0eb4ecee4 n/a (libxapian.so.30)
>> #1 0x00007fe0eb4f06fe n/a (libxapian.so.30)
>> #2 0x00007fe0eb4f7284 n/a (libxapian.so.30)
>> #3 0x00007fe0eb4161f8 _ZNK6Xapian7Enquire8Internal8get_msetEjjjPKNS_4RSetEPKNS_12MatchDeciderE (libxapian.so.30)
>> #4 0x00007fe0eb416466 _ZNK6Xapian7Enquire8get_msetEjjjPKNS_4RSetEPKNS_12MatchDeciderE (libxapian.so.30)
>> #5 0x00007fe0ebbc49ca n/a (libnotmuch.so.5)
>> #6 0x00007fe0ebbc527e notmuch_query_search_threads (libnotmuch.so.5)
>> #7 0x0000557fc9f05c68 n/a (notmuch)
>> #8 0x0000557fc9efa12c n/a (notmuch)
>> #9 0x00007fe0eb5d7153 __libc_start_main (libc.so.6)
>> #10 0x0000557fc9efa2ee n/a (notmuch)
>>
>> The type of query in question is the following: "not tag:notmuch-list
>> and to:notmuch@notmuchmail.org". It crashes, but only if there is a
>> matching message. Quoting the email address separately doesn't change
>> anything. I have several such queries for different lists in my post-new
>> hook, and the problem seems to apply to all of them.
>>
>> When I run the search with NOTMUCH_DEBUG_QUERY=1, I get the following
>> query information:
>>
>> Query string is:
>> not tag:notmuch-list and to:notmuch@notmuchmail.org
>> Exclude query is:
>> Query((Kdeleted OR Kspam))
>> Final query is:
>> Query(((Tmail AND ((<alldocuments> AND_NOT Knotmuch-list) AND (XTOnotmuch@1 PHRASE 3 XTOnotmuchmail@2 PHRASE 3 XTOorg@3))) AND_NOT (Kdeleted OR Kspam)))
>>
>> Does anyone have an idea where the problem could be or how to
>> investigate further?
>>
>> Thanks,
>> Sebastian
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-10-29 18:22 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-29 17:50 Segfault in libxapian when searching Sebastian Poeplau
2019-10-29 17:57 ` Sebastian Poeplau
2019-10-29 18:22 ` Sebastian Poeplau
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).