Valgrind points out error in vtkSocketCommunicator
This was found running the pvcs.HistogramSelection test with the server processes running in valgrind. This only appeared on one of the server processes.
==5854== Syscall param socketcall.sendto(msg) points to uninitialised byte(s)
==5854== at 0x7DEEB7F: send (send.c:26)
==5854== by 0x1C238365: vtkSocket::Send(void const*, int) (vtkSocket.cxx:567)
==5854== by 0x6C674A9: vtkSocketCommunicator::SendTagged(void const*, int, int, int, char const*) (vtkSocketCommunicator.cxx:745)
==5854== by 0x6C62DC0: vtkSocketCommunicator::SendVoidArray(void const*, long long, int, int, int) (vtkSocketCommunicator.cxx:292)
==5854== by 0x564C276: vtkCommunicator::Send(unsigned char const*, long long, int, int) (vtkCommunicator.h:160)
==5854== by 0x566A31A: vtkMultiProcessController::Send(unsigned char const*, long long, int, int) (vtkMultiProcessController.h:1617)
==5854== by 0x65B96E8: vtkPVSessionServer::GatherInformationInternal(unsigned int, char const*, unsigned int, vtkMultiProcessStream&) (vtkPVSessionServer.cxx:625)
==5854== by 0x65B932F: vtkPVSessionServer::OnClientServerMessageRMI(void*, int) (vtkPVSessionServer.cxx:575)
==5854== by 0x65B71BB: (anonymous namespace)::RMICallback(void*, void*, int, int) (vtkPVSessionServer.cxx:56)
==5854== by 0x6C4A4DC: vtkMultiProcessController::ProcessRMI(int, void*, int, int) (vtkMultiProcessController.cxx:768)
==5854== by 0x6C4A058: vtkMultiProcessController::ProcessRMIs(int, int) (vtkMultiProcessController.cxx:717)
==5854== by 0x69952CA: vtkTCPNetworkAccessManager::ProcessEventsInternal(unsigned long, bool) (vtkTCPNetworkAccessManager.cxx:268)
==5854== Address 0x37411921 is 129 bytes inside a block of size 258 alloc'd
==5854== at 0x4C2E0EF: operator new(unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==5854== by 0x5206427: __gnu_cxx::new_allocator<unsigned char>::allocate(unsigned long, void const*) (new_allocator.h:104)
==5854== by 0x52062F5: __gnu_cxx::__alloc_traits<std::allocator<unsigned char> >::allocate(std::allocator<unsigned char>&, unsigned long) (alloc_traits.h:182)
==5854== by 0x5206109: std::_Vector_base<unsigned char, std::allocator<unsigned char> >::_M_allocate(unsigned long) (stl_vector.h:170)
==5854== by 0x5205BD9: std::vector<unsigned char, std::allocator<unsigned char> >::_M_fill_insert(__gnu_cxx::__normal_iterator<unsigned char*, std::vector<unsigned char, std::allocator<unsigned char> > >, unsigned long, unsigned char const&) (vector.tcc:491)
==5854== by 0x5205857: std::vector<unsigned char, std::allocator<unsigned char> >::insert(__gnu_cxx::__normal_iterator<unsigned char*, std::vector<unsigned char, std::allocator<unsigned char> > >, unsigned long, unsigned char const&) (stl_vector.h:1073)
==5854== by 0x52055FC: std::vector<unsigned char, std::allocator<unsigned char> >::resize(unsigned long, unsigned char) (stl_vector.h:716)
==5854== by 0x11058E8F: vtkClientServerStream::Write(void const*, unsigned long) (vtkClientServerStream.cxx:245)
==5854== by 0x11062065: vtkClientServerStreamInternals::Write(vtkClientServerStream&, void const*, unsigned long) (vtkClientServerStream.cxx:181)
==5854== by 0x11064383: vtkClientServerStream& vtkClientServerStreamOperatorSL<double>(vtkClientServerStream*, double) (vtkClientServerStream.cxx:514)
==5854== by 0x11059E45: vtkClientServerStream::operator<<(double) (vtkClientServerStream.cxx:540)
==5854== by 0x697475B: vtkPVServerInformation::CopyToStream(vtkClientServerStream*) (vtkPVServerInformation.cxx:297)
I'm not sure if it is actually a problem or not, but it should eventually be investigated.