Hi Satya,
I have ensured that the initialization occurs before the data is
used/printed. So I believe memset is not required. I could give this a try
and see if it works. By the way, I figured out the error and it is a
improper incrementing of a variable.
Thanks
Santosh
On Tue, Mar 29, 2011 at 3:41 AM, <guptasa...@netzero.net> wrote:
> A memset immediately after the malloc but before the for loop should take
> care of this problem. The for loop may execute before your other nested
> initialization occurs.
>
> memset(matrix, 0, (size * sizeof(in)));
>
> Satya
> Sent from my Verizon Wireless BlackBerry
>
> -----Original Message-----
> From: Santosh Navale <santosh.iitm2...@gmail.com>
> Date: Mon, 28 Mar 2011 22:08:00
> To: Florian Krohm<brit...@acm.org>
> Cc: <valgrind-users@lists.sourceforge.net>
> Subject: Re: [Valgrind-users] Problem resolving a Valgrind reported error
>
>
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
>
------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
