OK. Then it is likely that there is a bug in our software.
As for the tests - it is a bit complicated. But if you are willing to spend
some time on it, we would be very happy. :-)
Get latest Knot DNS from git:
$ git clone https://gitlab.labs.nic.cz/labs/knot.git
Compile the server. We hit the
Dne Po 18. srpna 2014 10:25:42, Eliot Moss napsal(a):
On 8/18/2014 9:09 AM, Jan Včelák wrote:
I'm not rejecting that there is a problem in our code, but I want to make
sure that we are chasing a real bug.
You might want to verify that valgrind and your code have the same
notion of what
If you think it's a race, then the address sanitizer won't find it, I guess.
Rather, try the thread sanitizer.
http://clang.llvm.org/docs/ThreadSanitizer.html
Unfortunatelly, thread sanitizer does not support synchronization using memory
barriers. The same with Helgrind.
On Tue, Aug 19, 2014 at 5:59 PM, Milian Wolff m...@milianw.de wrote:
On Tuesday 19 August 2014 14:23:26 Jan Včelák wrote:
OK. Then it is likely that there is a bug in our software.
snip
I run the test case several times without Valgrind with address sanitizer.
But I didn't hit the problem.
On Tuesday 19 August 2014 14:23:26 Jan Včelák wrote:
OK. Then it is likely that there is a bug in our software.
snip
I run the test case several times without Valgrind with address sanitizer.
But I didn't hit the problem.
If you think it's a race, then the address sanitizer won't find it, I
On Tue, Aug 19, 2014 at 4:13 PM, Alexander Potapenko gli...@google.com wrote:
On Tue, Aug 19, 2014 at 5:59 PM, Milian Wolff m...@milianw.de wrote:
On Tuesday 19 August 2014 14:23:26 Jan Včelák wrote:
OK. Then it is likely that there is a bug in our software.
snip
I run the test case several
On 19.08.2014 04:37, Shaopeng Chen wrote:
Hey all,
I found a spelling mistake in the web page of FAQ(
http://valgrind.org/docs/manual/faq.html#faq.pronounce).
*1.1.**How do you pronounce Valgrind?*
The Val as in the world value. The grind is pronounced with a short
'i' -- ie.
On Tue, 2014-08-19 at 14:23 +0200, Jan Včelák wrote:
Compile the server. We hit the problem with the following configuration:
$ autoreconf -fi
$ export CC=gcc
$ export CFLAGS=-O0 -g -j4
$ ./configure --enable-recvmmsg=no \
--enable-lto=no \
--disable-fastparser
On Tue, 2014-08-19 at 21:44 +0200, David Faure wrote:
On Tuesday 19 August 2014 21:00:58 Philippe Waroquiers wrote:
On Tue, 2014-08-19 at 16:46 +0200, Roland Mainz wrote:
ThreadSanitizer won't comprehend the fence instructions inserted by
urcu.
I believe even Helgrind won't, because
On Tuesday 19 August 2014 21:00:58 Philippe Waroquiers wrote:
On Tue, 2014-08-19 at 16:46 +0200, Roland Mainz wrote:
ThreadSanitizer won't comprehend the fence instructions inserted by
urcu.
I believe even Helgrind won't, because these instructions do not imply
any happens-before
On Tue, 2014-08-19 at 22:11 +0200, David Faure wrote:
I'm still trying to find a way to annotate threadsafe-statics so that
helgrind doesn't complain about them.
What is a threadsafe-static ?
See older mail to this list, attached.
It doesn't use __thread anywhere, but rather lets
On 08/19/2014 02:31 PM, Jan Včelák wrote:
I believe the problem originates in some kind of race.
Try --fair-sched=yes to see if you can reproduce the problem more
often and/or more reliably.
J
--
Slashdot TV.
Video
On Tue, 2014-08-19 at 22:29 +0200, Philippe Waroquiers wrote:
It doesn't use __thread anywhere, but rather lets gcc take care of ensuring
thread-safety on static objects (like C++11 mandates, but it has been doing
so
for a long time already).
Quickly re-reading the mail, this is not
13 matches
Mail list logo
