From: Willem Jan Withagen <wjw@digiware.nl>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: AddressSanitizer
Date: Fri, 1 Apr 2016 16:46:20 +0200 [thread overview]
Message-ID: <56FE89BC.5040808@digiware.nl> (raw)
Hi
In my search for reasons why I have crashes I started using
AddressSanitizer with Clang (since that is native included)
https://github.com/google/sanitizers/wiki/AddressSanitizer,
Below the results which might indicate locations of possible trouble.
Would there be interest into looking into these further?
I know that some unitests under valgrind also complain about memory
leaks just because items are not properly free/deleted since they are
just tests.
But the ceph-mon container-overflow and the .libs/ceph-dencoder double
free are parts of the tree that are used outside the tests.
But I still have to find the flags to actually get the translation to
file codelines for this to be really useful.
--WjW
SUMMARY: AddressSanitizer: alloc-dealloc-mismatch
(/usr/srcs/Ceph/work/ceph/src/unittest_erasure_code_isa+0x7fea8b)
SUMMARY: AddressSanitizer: alloc-dealloc-mismatch
(/usr/srcs/Ceph/work/ceph/src/unittest_erasure_code_plugin_isa+0x7e9d0b)
SUMMARY: AddressSanitizer: alloc-dealloc-mismatch
(/usr/srcs/Ceph/work/ceph/src/unittest_erasure_code_shec+0x8144cb)
SUMMARY: AddressSanitizer: alloc-dealloc-mismatch
(/usr/srcs/Ceph/work/ceph/src/unittest_erasure_code_shec_all+0x8021ab)
SUMMARY: AddressSanitizer: alloc-dealloc-mismatch
(/usr/srcs/Ceph/work/ceph/src/unittest_erasure_code_shec_thread+0x7fb78b)
SUMMARY: AddressSanitizer: alloc-dealloc-mismatch
(/usr/srcs/Ceph/work/ceph/src/unittest_erasure_code_shec_arguments+0x7fd74b)
SUMMARY: AddressSanitizer: alloc-dealloc-mismatch
(/usr/srcs/Ceph/work/ceph/src/unittest_erasure_code_plugin_shec+0x7e98db)
SUMMARY: AddressSanitizer: heap-use-after-free
(/usr/srcs/Ceph/work/ceph/src/unittest_pglog+0x92722f)
SUMMARY: AddressSanitizer: dynamic-stack-buffer-overflow
(/usr/srcs/Ceph/work/ceph/src/unittest_lfnindex+0x8ee69f)
SUMMARY: AddressSanitizer: stack-buffer-overflow
(/usr/srcs/Ceph/work/ceph/src/unittest_utf8+0x5ff392)
SUMMARY: AddressSanitizer: container-overflow
(/usr/srcs/Ceph/work/ceph/src/ceph-mon+0xb591b1)
SUMMARY: AddressSanitizer: double-free
(/usr/srcs/Ceph/work/ceph/src/.libs/ceph-dencoder+0x8b1fcb)
next reply other threads:[~2016-04-01 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 14:46 Willem Jan Withagen [this message]
2016-04-01 22:19 ` AddressSanitizer Gregory Farnum
2016-04-02 2:43 ` AddressSanitizer Evgeniy Firsov
2016-04-02 9:20 ` AddressSanitizer 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=56FE89BC.5040808@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.