From: Mykola Golub <mgolub@mirantis.com>
To: Willem Jan Withagen <wjw@digiware.nl>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Hard to debug problem with ceph_erasure_code
Date: Fri, 1 Apr 2016 08:12:06 +0300 [thread overview]
Message-ID: <20160401051205.GA29567@gmail.com> (raw)
In-Reply-To: <56FD5A15.1080507@digiware.nl>
On Thu, Mar 31, 2016 at 07:10:45PM +0200, Willem Jan Withagen wrote:
> Does anybody have suggestions as how to track/debug this?
valgrind?
--
Mykola Golub
next prev parent reply other threads:[~2016-04-01 5:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 17:10 Hard to debug problem with ceph_erasure_code Willem Jan Withagen
2016-04-01 5:12 ` Mykola Golub [this message]
2016-04-01 9:34 ` Willem Jan Withagen
2016-04-01 12:22 ` Willem Jan Withagen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160401051205.GA29567@gmail.com \
--to=mgolub@mirantis.com \
--cc=ceph-devel@vger.kernel.org \
--cc=wjw@digiware.nl \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox