From: Willem Jan Withagen <wjw@digiware.nl>
To: Mykola Golub <mgolub@mirantis.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Hard to debug problem with ceph_erasure_code
Date: Fri, 1 Apr 2016 11:34:16 +0200 [thread overview]
Message-ID: <56FE4098.8000209@digiware.nl> (raw)
In-Reply-To: <20160401051205.GA29567@gmail.com>
On 1-4-2016 07:12, Mykola Golub wrote:
> 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?
>
Yup, tried that one, but it is sort of hard to find an intermittent
erroneous write. I tried --track-addr=<addr of m_exp_len> But most of
the time it is only written at exact the code line it is supposed to be
written. So no info there.
So perhaps I need a different set of tests?
On average I need about 600 runs to catch one SIGSEGV.
BTW: tried it on 2 FreeBSD systems, and on both the behaviour is
identical. So it has got to be the code. And since 65000 runs on Linux
give no errors, it is also typical for the combo
FreeBSD/Clang/FreeBSD-packages.
--WjW
next prev parent reply other threads:[~2016-04-01 9:34 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
2016-04-01 9:34 ` Willem Jan Withagen [this message]
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=56FE4098.8000209@digiware.nl \
--to=wjw@digiware.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=mgolub@mirantis.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.