From: David Bremner <david@tethera.net>
To: Brian May <brian@linuxpenguins.xyz>, notmuch@notmuchmail.org
Subject: Re: muchsync segfault
Date: Mon, 28 Sep 2020 06:44:36 -0300 [thread overview]
Message-ID: <87wo0e9qwr.fsf@tethera.net> (raw)
In-Reply-To: <8736327lse.fsf@silverfish.pri>
Brian May <brian@linuxpenguins.xyz> writes:
>
> Anything else I should try?
>
Generic advice would be to run in gdb and get a backtrace, assuming you
have debugging symbols.
d
next prev parent reply other threads:[~2020-09-28 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 1:05 muchsync segfault Brian May
2020-09-28 9:44 ` David Bremner [this message]
2020-09-28 11:11 ` Brian May
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=87wo0e9qwr.fsf@tethera.net \
--to=david@tethera.net \
--cc=brian@linuxpenguins.xyz \
--cc=notmuch@notmuchmail.org \
/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).