Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Archive
C Programming
uninitialized memory read
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
[QUOTE="parag, post: 3809910"] Nope, My Valgrind output did not find anything Valgrind version ( valgrind-3.2.0 ) output valgrind --tool=memcheck --show-reachable=yes --undef-value- errors=yes ./a.out ==31752== Memcheck, a memory error detector. ==31752== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al. ==31752== Using LibVEX rev 1606, a library for dynamic binary translation. ==31752== Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP. ==31752== Using valgrind-3.2.0, a dynamic binary instrumentation framework. ==31752== Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward et al. ==31752== For more details, rerun with: -v ==31752== 31 and the value is maskt ==31752== ==31752== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 11 from 5) ==31752== malloc/free: in use at exit: 0 bytes in 0 blocks. ==31752== malloc/free: 0 allocs, 0 frees, 0 bytes allocated. ==31752== For counts of detected errors, rerun with: -v ==31752== All heap blocks were freed -- no leaks are possible. looks like nothing [/QUOTE]
Verification
Post reply
Forums
Archive
Archive
C Programming
uninitialized memory read
Top