[Xapian-tickets] [Xapian] #796: Segmentation fault

[Xapian]

#796: Segmentation fault
----------------------+---------------------------
 Reporter:  zangetsu  |             Owner:  olly
     Type:  defect    |            Status:  closed
 Priority:  normal    |         Milestone:  1.4.14
Component:  Matcher   |           Version:  1.4.13
 Severity:  normal    |        Resolution:  fixed
 Keywords:            |        Blocked By:
 Blocking:            |  Operating System:  All
----------------------+---------------------------

Comment (by zangetsu):

 Ok, I got two queries where it segfaulted. I've adjusted the tag names and
 values, but the rest is faithful. Also note that the "foobar" of the first
 example is not the same as the one in the second.

 {{{
 NOTMUCH_DEBUG_QUERY=1 ./notmuch tag +foobar to:foo-bar@
 Query string is:
 ( to:foo-bar@ ) and (not tag:foobar)
 Exclude query is:
 Query()
 Final query is:
 Query((Tmail AND ((XTOfoo at 1 PHRASE 2 XTObar at 2) AND (<alldocuments> AND_NOT
 Kfoobar))))
 }}}

 {{{
 NOTMUCH_DEBUG_QUERY=1 ./notmuch search custom:one.two.three.four AND NOT
 tag:foobar
 Query string is:
 custom:one.two.three.four AND NOT tag:foobar
 Exclude query is:
 Query((Kdeleted OR Kspam))
 Final query is:
 Query(((Tmail AND ((XUcustom:one at 1 PHRASE 4 XUcustom:two at 2 PHRASE 4
 XUcustom:three at 3 PHRASE 4 XUcustom:four at 4) AND_NOT Kfoobar)) AND_NOT
 (Kdeleted OR Kspam)))
 }}}

 These were two specific things that kept failing, however. All of my other
 tagging rules (the vast majority) still worked fine, so it's possible that
 some very specific things came together in some emails.

 I built xapian with `-g`, but the resulting stack trace is just roughly
 the one from my initial report. I can't easily use `gdb` here, due to SIP,
 but let me know if there's an easy way to generate that backtrace that I'm
 missing.

--
Ticket URL: <https://trac.xapian.org/ticket/796#comment:5>
Xapian <https://xapian.org/>
Xapian