[vtkusers] vtkStringArray problem
mbcx9rb9
richard.j.brown at live.co.uk
Wed Dec 3 11:04:29 EST 2014
Cory,
Valgrind output looks like this (I omitted test1->test158):
==17464== Memcheck, a memory error detector
==17464== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==17464== Using Valgrind-3.11.0.SVN and LibVEX; rerun with -h for copyright
info
==17464== Command: ./StringArrayTest
==17464==
--17464-- ./StringArrayTest:
--17464-- dSYM directory is missing; consider using --dsymutil=yes
--17464-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option
--17464-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2
times)
--17464-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4
times)
==17464== Conditional jump or move depends on uninitialised value(s)
==17464== at 0x10085EC3F: _platform_memchr$VARIANT$Haswell (in
/usr/lib/system/libsystem_platform.dylib)
==17464== by 0x100652BB6: __sfvwrite (in
/usr/lib/system/libsystem_c.dylib)
==17464== by 0x1006530CA: fwrite (in /usr/lib/system/libsystem_c.dylib)
==17464== by 0x10039ED29: std::__1::__stdoutbuf<char>::overflow(int) (in
/usr/lib/libc++.1.dylib)
==17464== by 0x10039491C: std::__1::basic_streambuf<char,
std::__1::char_traits<char> >::xsputn(char const*, long) (in
/usr/lib/libc++.1.dylib)
==17464== by 0x10002B135: std::__1::ostreambuf_iterator<char,
std::__1::char_traits<char> > std::__1::__pad_and_output<char,
std::__1::char_traits<char> >(std::__1::ostreambuf_iterator<char,
std::__1::char_traits<char> >, char const*, char const*, char const*,
std::__1::ios_base&, char) (in /usr/local/lib/libvtkCommonCore-6.1.1.dylib)
==17464== by 0x10002AFAC: std::__1::basic_ostream<char,
std::__1::char_traits<char> >& std::__1::__put_character_sequence<char,
std::__1::char_traits<char> >(std::__1::basic_ostream<char,
std::__1::char_traits<char> >&, char const*, unsigned long) (in
/usr/local/lib/libvtkCommonCore-6.1.1.dylib)
==17464== by 0x100001F06: main (in ./StringArrayTest)
==17464==
test0
...
test159
==17464==
==17464== HEAP SUMMARY:
==17464== in use at exit: 41,598 bytes in 421 blocks
==17464== total heap usage: 637 allocs, 216 frees, 82,544 bytes allocated
==17464==
==17464== LEAK SUMMARY:
==17464== definitely lost: 16 bytes in 1 blocks
==17464== indirectly lost: 0 bytes in 0 blocks
==17464== possibly lost: 13,122 bytes in 116 blocks
==17464== still reachable: 28,460 bytes in 304 blocks
==17464== suppressed: 0 bytes in 0 blocks
==17464== Rerun with --leak-check=full to see details of leaked memory
==17464==
==17464== For counts of detected and suppressed errors, rerun with: -v
==17464== Use --track-origins=yes to see where uninitialised values come
from
==17464== ERROR SUMMARY: 1010 errors from 1 contexts (suppressed: 0 from 0)
--
View this message in context: http://vtk.1045678.n5.nabble.com/vtkStringArray-problem-tp5729638p5729657.html
Sent from the VTK - Users mailing list archive at Nabble.com.
More information about the vtkusers
mailing list