[Gluster-devel] catching unitialized structures

Kaleb Keithley kkeithle at redhat.com
Tue Apr 30 02:08:08 UTC 2013

I don't suppose anyone has run any of gluster under the helgrind option of valgrind?

----- Original Message -----
From: "Vijay Bellur" <vbellur at redhat.com>
To: "Vijay Bellur" <vbellur at redhat.com>
Cc: gluster-devel at nongnu.org
Sent: Monday, April 29, 2013 1:38:34 PM
Subject: Re: [Gluster-devel] catching unitialized structures

On 04/29/2013 11:05 PM, Vijay Bellur wrote:
> On 04/29/2013 10:31 PM, Emmanuel Dreyfus wrote:
>> Hi
>> I found an uninitialized mutex and I am tracking another one. This is
>> not the first time I hit this kind of problem, which is invisible to
>> Linux developpers since Linux allows using an uninitialized mutex.
>> I suggest chaning GF_CALLOC and friends so that it fills memory
>> with 0xdeadbeef during developement cycles. That would help people
>> catching that kind og issues earlier.
> Maybe with -DDEBUG?

Hit send a bit too fast. There are a lot of places where we make an 
implicit assumption that GF_CALLOC and the likes memset the memory area 
to zero. It might not be an easy thing to achieve after all.


Gluster-devel mailing list
Gluster-devel at nongnu.org

More information about the Gluster-devel mailing list