I don't know if this is a bug, but 
I used valgrind on our application and I got the
following message

==18223== Memcheck, a memory error detector.
==18223== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al.
==18223== Using LibVEX rev 1606, a library for dynamic binary translation.
==18223== Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP.
==18223== Using valgrind-3.2.0, a dynamic binary instrumentation framework.
==18223== Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward et al.
==18223== For more details, rerun with: -v
==18223== 
==18223== Conditional jump or move depends on uninitialised value(s)
==18223==    at 0x4B1C8FF: GSFormat (GSFormat.m:291)
==18223==    by 0x4B33F85: 
_i_GSPlaceholderString__initWithFormat_locale_arguments_ (GSString.m:502)
==18223==    by 0x4C064E8: _c_NSString__stringWithFormat_ (NSZone.h:281)
==18223==    by 0x4BE0E0A: _i_NSProcessInfo__globallyUniqueString 
(NSProcessInfo.m:913)
==18223==    by 0x400950: main (NSPT.m:7)
==18223== 
==18223== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 5 from 2)
==18223== malloc/free: in use at exit: 479,919 bytes in 8,691 blocks.
==18223== malloc/free: 13,224 allocs, 4,533 frees, 1,903,779 bytes allocated.
==18223== For counts of detected errors, rerun with: -v
==18223== searching for pointers to 8,691 not-freed blocks.
==18223== checked 1,496,552 bytes.
==18223== 
==18223== LEAK SUMMARY:
==18223==    definitely lost: 4,624 bytes in 290 blocks.
==18223==      possibly lost: 8,078 bytes in 193 blocks.
==18223==    still reachable: 467,217 bytes in 8,208 blocks.
==18223==         suppressed: 0 bytes in 0 blocks.
==18223== Use --leak-check=full to see details of leaked memory.


This was  ran with the attached test program.
I have looked shortly at the source and got no real insight what might be the 
problem (if there is any.)

Attachment: NSPT.tar.gz
Description: Test program

_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep

Reply via email to