FS#64273 - [xapian-core] notmuch core dumps in libxapian after upgrading xapian-core to 1:1.4.13-1

Attached to Project: Arch Linux
Opened by Eric Blau (eblau) - Saturday, 26 October 2019, 12:14 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 24 November 2019, 09:48 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:

After upgrading xapian-core from 1:1.4.12-1 -> 1:1.4.13-1, I'm getting constant notmuch core dumps. I have a script that runs "notmuch new", applies various tags and then removes the "new" tag. It core dumps here:

$ notmuch new
$ notmuch tag +to-me tag:new and to:eblau@eblau.com and not tag:to-me
/home/eblau/bin/my-notmuch: line 92: 68574 Segmentation fault (core dumped)

Here's the backtrace:

Oct 26 08:12:00 eric-pc systemd-coredump[68576]: Process 68574 (notmuch) of user 1000 dumped core.

Stack trace of thread 68574:
#0 0x00007f6e18276ee4 n/a (libxapian.so.30)
#1 0x00007f6e1827a6fe n/a (libxapian.so.30)
#2 0x00007f6e182810a2 n/a (libxapian.so.30)
#3 0x00007f6e181a01f8 _ZNK6Xapian7Enquire8Internal8get_msetEjjjPKNS_4RSetEPKNS_12MatchDeciderE (libxapian.so.30)
#4 0x00007f6e181a0466 _ZNK6Xapian7Enquire8get_msetEjjjPKNS_4RSetEPKNS_12MatchDeciderE (libxapian.so.30)
#5 0x00007f6e1894e9ca n/a (libnotmuch.so.5)
#6 0x0000563df6887ca2 n/a (notmuch)
#7 0x0000563df688821a n/a (notmuch)
#8 0x0000563df687812c n/a (notmuch)
#9 0x00007f6e18361153 __libc_start_main (libc.so.6)
#10 0x0000563df68782ee n/a (notmuch)


Downgrading to xapian-core 1:1.4.12-1 resolves the problem.
This task depends upon

Closed by  Antonio Rojas (arojas)
Sunday, 24 November 2019, 09:48 GMT
Reason for closing:  Fixed
Additional comments about closing:  xapian-core 1.4.14
Comment by Eric Blau (eblau) - Monday, 28 October 2019, 18:12 GMT
The issue is resolved after upgrading notmuch and notmuch-runtime from 0.29.1-1 to 0.29.2-1. I guess an ABI incompatibility was inadvertently introduced in libxapian.so from the upgrade.
Comment by Eric Blau (eblau) - Monday, 28 October 2019, 18:16 GMT
Sorry, I spoke too soon. The problem occurs with notmuch and notmuch-runtime 0.29.2-1 with xapian-core 1:1.4.13-1.

Stack trace of thread 790586:
#0 0x00007ff04e79fee4 n/a (libxapian.so.30)
#1 0x00007ff04e7a36fe n/a (libxapian.so.30)
#2 0x00007ff04e7aa0a2 n/a (libxapian.so.30)
#3 0x00007ff04e6c91f8 _ZNK6Xapian7Enquire8Internal8get_msetEjjjPKNS_4RSetEPKNS_12MatchDeciderE (libxapian.so.30)
#4 0x00007ff04e6c9466 _ZNK6Xapian7Enquire8get_msetEjjjPKNS_4RSetEPKNS_12MatchDeciderE (libxapian.so.30)
#5 0x00007ff04ee779ca n/a (libnotmuch.so.5)
#6 0x00005585bbaf2ca2 n/a (notmuch)
#7 0x00005585bbaf321a n/a (notmuch)
#8 0x00005585bbae312c n/a (notmuch)
#9 0x00007ff04e88a153 __libc_start_main (libc.so.6)
#10 0x00005585bbae32ee n/a (notmuch)
Comment by Eric Blau (eblau) - Monday, 28 October 2019, 18:21 GMT
This issue was reported upstream: https://trac.xapian.org/ticket/796

Looks like it is slated to be fixed in xapian 1.4.14. I'll stick with 1.4.12 until that time.
Comment by SpicyCat (SpicyCat) - Wednesday, 06 November 2019, 07:10 GMT
I can confirm this bug. It happens on my PC too. I use Manjaro

> Looks like it is slated to be fixed in xapian 1.4.14. I'll stick with 1.4.12 until that time.
→ Same here. xapian-core is in my ignore list now.

Loading...