From: Willem Jan Withagen <wjw@digiware.nl>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Crashes with unittest_dencoder
Date: Fri, 2 Jun 2017 01:00:32 +0200 [thread overview]
Message-ID: <66fafc3c-a5dd-405d-a521-597fe524d1e3@digiware.nl> (raw)
Any hints on what changes in the current code generates the illegal
memaccess in the trace below?
Lots of tests fail, and I guess that mst have to do with this.
--WjW
Program received signal SIGSEGV, Segmentation fault.
0x00000008025e693e in std::__1::__atomic_base<unsigned long,
true>::fetch_add (this=0x108803637688,
__op=1, __m=std::__1::memory_order_seq_cst) at
/usr/include/c++/v1/atomic:980
980 {return __c11_atomic_fetch_add(&this->__a_, __op, __m);}
(gdb) bt
#0 0x00000008025e693e in std::__1::__atomic_base<unsigned long,
true>::fetch_add (this=0x108803637688,
__op=1, __m=std::__1::memory_order_seq_cst) at
/usr/include/c++/v1/atomic:980
#1 std::__1::__atomic_base<unsigned long, true>::operator+=
(this=0x108803637688, __op=1)
at /usr/include/c++/v1/atomic:1025
#2 mempool::pool_t::adjust_count (this=0x108803637680, items=1, bytes=42)
at /home/jenkins/workspace/ceph-master/src/common/mempool.cc:85
#3 0x00000008024f1bfb in ceph::buffer::raw::reassign_to_mempool
(this=0x1076130, pool=-1)
at /home/jenkins/workspace/ceph-master/src/common/buffer.cc:196
#4 0x00000008024e1b19 in ceph::buffer::list::reserve
(this=0x7fffffffd040, prealloc=42)
at /home/jenkins/workspace/ceph-master/src/common/buffer.cc:1772
#5 0x00000000004d0ad5 in ceph::buffer::list::list (this=0x7fffffffd040,
prealloc=42)
at /home/jenkins/workspace/ceph-master/src/include/buffer.h:662
#6 0x00000000004b4114 in Legacy::encode_n (n=42, segments=...)
at /home/jenkins/workspace/ceph-master/src/test/test_denc.cc:610
#7 0x00000000004b4d22 in
denc_no_copy_if_segmented_and_lengthy_Test::TestBody (this=0x1068070)
at /home/jenkins/workspace/ceph-master/src/test/test_denc.cc:633
#8 0x00000000005ea62e in
testing::internal::HandleSehExceptionsInMethodIfSupported<testing::Test,
void> (
object=0x1068070, method=&virtual testing::Test::TestBody(),
location=0x6156ee "the test body")
at
/home/jenkins/workspace/ceph-master/src/googletest/googletest/src/gtest.cc:2402
#9 0x00000000005ccabb in
testing::internal::HandleExceptionsInMethodIfSupported<testing::Test,
void> (
object=0x1068070, method=&virtual testing::Test::TestBody(),
location=0x6156ee "the test body")
at
/home/jenkins/workspace/ceph-master/src/googletest/googletest/src/gtest.cc:2438
#10 0x00000000005885c6 in testing::Test::Run (this=0x1068070)
at
/home/jenkins/workspace/ceph-master/src/googletest/googletest/src/gtest.cc:2474
#11 0x000000000058ad0d in testing::TestInfo::Run (this=0x106edd0)
at
/home/jenkins/workspace/ceph-master/src/googletest/googletest/src/gtest.cc:2656
#12 0x000000000058bfcc in testing::TestCase::Run (this=0x106e0d0)
at
/home/jenkins/workspace/ceph-master/src/googletest/googletest/src/gtest.cc:2774
#13 0x00000000005a2e8c in testing::internal::UnitTestImpl::RunAllTests
(this=0x1072000)
at
/home/jenkins/workspace/ceph-master/src/googletest/googletest/src/gtest.cc:4649
#14 0x00000000005ed4be in
testing::internal::HandleSehExceptionsInMethodIfSupported<testing::internal::UnitTestImpl,
bool> (object=0x1072000,
method=(bool
(testing::internal::UnitTestImpl::*)(testing::internal::UnitTestImpl *
const)) 0x5a2af0 <testing::internal::UnitTestImpl::RunAllTests()>,
location=0x615d71 "auxiliary test code (environments or event
listeners)")
at
/home/jenkins/workspace/ceph-master/src/googletest/googletest/src/gtest.cc:2402
next reply other threads:[~2017-06-01 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 23:00 Willem Jan Withagen [this message]
2017-06-01 23:27 ` Crashes with unittest_dencoder Brad Hubbard
2017-06-02 0:23 ` Willem Jan Withagen
2017-06-02 0:46 ` Willem Jan Withagen
2017-06-02 7:08 ` Brad Hubbard
2017-06-02 7: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=66fafc3c-a5dd-405d-a521-597fe524d1e3@digiware.nl \
--to=wjw@digiware.nl \
--cc=ceph-devel@vger.kernel.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.
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.