[Paraview] Custom plugin reader with time series

[Dominik Szczerba]

YES if I recompile PV3 with system hdf5 (1.6.7) the problem does not 
occur anymore. It is compatible with my much former notion of the 
problem NOT happening outside the PV plugin framework, because my own 
code used 1.6.7. So the problem is the outdated hdf5 version used by PV 
(1.6.5) and/or its conflict with PV.

If I am able to maintain this conclusion for a few days I will file a 
bug report.

Thanks Mike,
Dominik

Dominik Szczerba wrote:
> Attached below. The line in my code (HDF5Reader.cxx:493) is:
> 
> status = H5Dread(dataset, H5T_NATIVE_INT, H5S_ALL, H5S_ALL, H5P_DEFAULT, 
> (int*)data);
> 
> I am able to reproduce that this happens if and only if the underlying 
> hdf5 dataset is chunked.
> 
> -- Dominik
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x44ff0980 (LWP 15040)]
> 0x4231c68d in H5S_hyper_adjust_u ()
>    from /scratch/domel/build/ParaView3-20080729/bin/libvtkhdf5.so
> (gdb) bt
> #0  0x4231c68d in H5S_hyper_adjust_u ()
>    from /scratch/domel/build/ParaView3-20080729/bin/libvtkhdf5.so
> #1  0x42305f73 in H5D_create_chunk_map ()
>    from /scratch/domel/build/ParaView3-20080729/bin/libvtkhdf5.so
> #2  0x4230883f in H5D_chunk_read ()
>    from /scratch/domel/build/ParaView3-20080729/bin/libvtkhdf5.so
> #3  0x42309a69 in H5Dread ()
>    from /scratch/domel/build/ParaView3-20080729/bin/libvtkhdf5.so
> #4  0x456e3d11 in HDF5::HDF5Reader::readData (this=0xbffe4808, 
> name=@0xbffe4830)
>     at /home/domel/src/common/HDF5++/HDF5Reader.cxx:493
> #5  0x456e56ce in HDF5::HDF5Reader::read (this=0xbffe4808, m=@0xbffe47f4,
>     name=@0xbffe4830) at /home/domel/src/common/HDF5++/HDF5Reader.cxx:278
> #6  0x456dc3bf in vtkHDF5UnstructuredGridReader::RequestData 
> (this=0x8e8c700,
>     outputVector=0x8e8c6e0)
>     at /home/domel/src/mesh/vtk/vtkHDF5UnstructuredGridReader.cxx:343
> #7  0x447f03f2 in vtkUnstructuredGridAlgorithm::ProcessRequest ()
>    from 
> /scratch/domel/build/ParaView3-20080729/bin/libvtkFiltering.so.pv3.3
> #8  0x446df412 in vtkExecutive::CallAlgorithm ()
>    from 
> /scratch/domel/build/ParaView3-20080729/bin/libvtkFiltering.so.pv3.3
> #9  0x446d708d in vtkDemandDrivenPipeline::ExecuteData ()
>    from 
> /scratch/domel/build/ParaView3-20080729/bin/libvtkFiltering.so.pv3.3
> #10 0x446b7030 in vtkCompositeDataPipeline::ExecuteData ()
>    from 
> /scratch/domel/build/ParaView3-20080729/bin/libvtkFiltering.so.pv3.3
> #11 0x446da696 in vtkDemandDrivenPipeline::ProcessRequest ()
>    from 
> /scratch/domel/build/ParaView3-20080729/bin/libvtkFiltering.so.pv3.3
> #12 0x447cca43 in vtkStreamingDemandDrivenPipeline::ProcessRequest ()
>    from 
> /scratch/domel/build/ParaView3-20080729/bin/libvtkFiltering.so.pv3.3
> 
> 
> Mike Jackson wrote:
>> Can you run ParaView in a debugger or attach to a running instance of 
>> paraview with a debugger, then trigger the bug? Most debuggers will 
>> break on a segfault and then you can track down the issue from there.
>>
> 

-- 
Dominik Szczerba, Ph.D.
Foundation for Research
on Information Technologies in Society
http://www.itis.ethz.ch