On 06/03/2011 11:35 PM, durga prasad wrote: > I had a test application with a memory leak of 100 bytes.When I run the > valgrind with the > test application its not showing the memory leak
Post the source code. It can't be that big, and it might not have any actual leak. and also its giving segmentation fault on the target [_after_ this:] > ==647== Invalid read of size 4 > ==647== at 0x4004D48: _dl_get_ready_to_run (in > /lib/ld-uClibc-0.9.30-nptl.so <http://ld-uclibc-0.9.30-nptl.so/>) > ==647== Address 0xbd6b9a54 is just below the stack ptr. To suppress, use: > --workaround-gcc296-bugs=yes A SIGSEGV is likely after a reading a pointer from the unprotected side of $sp. -- ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
