Re: muchsync segfault

2020-09-28 Thread Brian May
David Bremner  writes:

> Generic advice would be to run in gdb and get a backtrace, assuming you
> have debugging symbols.

Somebody else via private reply suggested I try the git version.

So far it looks like that has solved the problem.

Thanks
-- 
Brian May 
https://linuxpenguins.xyz/brian/
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org


Re: muchsync segfault

2020-09-28 Thread David Bremner
Brian May  writes:
>
> Anything else I should try?
>

Generic advice would be to run in gdb and get a backtrace, assuming you
have debugging symbols.

d
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org


muchsync segfault

2020-09-27 Thread Brian May
Hello all,

muchsync is segfaulting when I run it on a particular box:

$ muchsync -v silverfish.local   
[notmuch] No new mail.
synchronizing muchsync database with Xapian... 0.011202 (+0.011202)
starting scan of Xapian database... 0.011269 (+0.67)
opened Xapian... 0.011611 (+0.000342)
scanned message IDs... 0.162030 (+0.150420)
scanned tags... 0.175126 (+0.013096)
scanned directories in xapian... 0.175315 (+0.000189)
scanned filenames in xapian... 0.175394 (+0.79)
[SERVER] [notmuch] No new mail.
adjusted link counts... 0.226647 (+0.051253)
finished synchronizing muchsync database with Xapian... 0.235871 (+0.009224)
received server's version vector... 0.877723 (+0.641851)
received hashes of new files... 1.176468 (+0.298746)
[1]64563 segmentation fault  muchsync -v silverfish.local

How do I resolve?

I tried

$ notmuch reindex '*'

But this doesn't appear to have helped.

Anything else I should try?

Regards
-- 
Brian May 
https://linuxpenguins.xyz/brian/
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org