On Thu, Jul 16, 2009 at 7:47 PM, Nicholas
Nethercote wrote:
> On Fri, Jul 17, 2009 at 2:16 AM, Zachary Turner
> wrote:
>> --track-origins=yes I find that the memory it's claiming is
>> uninitialized comes from sbrk(). As far as I can tell (please correct
>> me i
When I build any program (including an empty main function) using gcc
-static I get enormous amounts of errors in valgrind. After some
investigation and asking around I think that at least a large portion
of them are incorrect. In particular, I get many errors about
uninitialized memory and condi
On Tue, Jul 14, 2009 at 1:07 PM, Colin Miller wrote:
> Zachary Turner wrote:
>>
>> On Tue, Jul 14, 2009 at 12:27 PM, Colin Miller
>> wrote:
>>
>> ==7439== Use of uninitialised value of size 4
>> ==7439== at 0x82D32D6: _int_malloc (in /usr/sbin/snip/bin/sn
On Tue, Jul 14, 2009 at 12:27 PM, Colin Miller wrote:
> Zachary Turner wrote:
>> Hello,
>>
>> I'm somewhat a valgrind noob, so apologies if this is a RTFM question.
>> I did search around however and did not see anything definitive about
>> this. I ran valg
Hello,
I'm somewhat a valgrind noob, so apologies if this is a RTFM question.
I did search around however and did not see anything definitive about
this. I ran valgrind on an app I have and it generated thousands of
spurious warnings. I know I can create a .supp file to suppress these,
but my qu
