On 3/28/2011 6:26 PM, Santosh Navale wrote:
Hi,
The following is the message I get when I run valgrind on my C code.
==16455== Use of uninitialised value of size 8
==16455==at 0x4E6A76B: _itoa_word (_itoa.c:195)
==16455==by 0x4E6B9B8: vfprintf (vfprintf.c:1613)
==16455==by 0x4E75869
> As far as I know, this one of the ways of declaring a 2D matrix in C. ... The
> initialization happens in another nested for loop.
So far you have not shown the code that establishes a value for each
matrix[row][j] when 0 <= j < size and 0 <= row < size.
Memcheck's complaint is about the _
Hi Florian,
Thanks for the suggestion. As far as I know, this one of the ways of
declaring a 2D matrix in C. Please correct me if I am wrong. The
initialization happens in another nested for loop.
Thanks
Santosh
On Mon, Mar 28, 2011 at 9:07 PM, Florian Krohm wrote:
> On 03/28/2011 09:26 PM, Sa
On 03/28/2011 09:26 PM, Santosh Navale wrote:
> Hi,
>
> The following is the message I get when I run valgrind on my C code.
>
> ==16455== Use of uninitialised value of size 8
> ==16455==at 0x4E6A76B: _itoa_word (_itoa.c:195)
> ==16455==by 0x4E6B9B8: vfprintf (vfprintf.c:1613)
> ==16455==
Hi,
The following is the message I get when I run valgrind on my C code.
==16455== Use of uninitialised value of size 8
==16455==at 0x4E6A76B: _itoa_word (_itoa.c:195)
==16455==by 0x4E6B9B8: vfprintf (vfprintf.c:1613)
==16455==by 0x4E75869: printf (printf.c:35)
==16455==by 0x40083
On Monday, March 28, 2011, Bart Van Assche wrote:
> On Mon, Mar 28, 2011 at 6:32 PM, Julian Seward wrote:
> > On Monday, March 28, 2011, Piotr Jaroszyński wrote:
> > > I think the proper solution is to add __attribute__((unused)) to
> > > _qzz_res. What do you think?
> >
> > Yes. I just committe
Howdy,
I'm trying to check for leaks in a program I've written, using "valgrind
--leak-check=full ...". When my program stays within relatively small
memory usage, that is, less than 2G total, valgrind has no complaints.
However, one of my test cases involves my program allocating a total of
abo
On Monday, March 28, 2011, Bart Van Assche wrote:
> On Mon, Mar 28, 2011 at 6:32 PM, Julian Seward wrote:
> > On Monday, March 28, 2011, Piotr Jaroszyński wrote:
> > > I think the proper solution is to add __attribute__((unused)) to
> > > _qzz_res. What do you think?
> >
> > Yes. I just committe
On Mon, Mar 28, 2011 at 6:32 PM, Julian Seward wrote:
>
> On Monday, March 28, 2011, Piotr Jaroszyński wrote:
> > I think the proper solution is to add __attribute__((unused)) to
> > _qzz_res. What do you think?
>
> Yes. I just committed exactly such cleanups (r11673). Could
> you try it, to see
2011/3/28 Julian Seward :
> On Monday, March 28, 2011, Piotr Jaroszyński wrote:
>> I think the proper solution is to add __attribute__((unused)) to
>> _qzz_res. What do you think?
>
> Yes. I just committed exactly such cleanups (r11673). Could
> you try it, to see if that also makes your compiles
On Monday, March 28, 2011, Piotr Jaroszyński wrote:
> I think the proper solution is to add __attribute__((unused)) to
> _qzz_res. What do you think?
Yes. I just committed exactly such cleanups (r11673). Could
you try it, to see if that also makes your compiles quiet again?
J
-
Hello,
the valgrind.h header imported from the project causes set but not
used warnings with gcc 4.6.0 when NVALGRIND is defined.
The culprit are VALGRIND_MALLOCLIKE_BLOCK, VALGRIND_FREELIKE_BLOCK and
similar macros:
error: variable ‘_qzz_res’ set but not used [-Werror=unused-but-set-variable]
I
12 matches
Mail list logo