Hi, My bad :(, Yes it does work with the -dr argument. There is no additional output on the console.
Is there a way to make it work without the -dr argument? Philipp On 23.01.2017 20:18, Utkarsh Ayachit wrote: > Philipp, > > The "-dr" was a command line argument to ParaView, not for building ParaView. > >> ./bin/paraview -dr > Utkarsh > > On Mon, Jan 23, 2017 at 2:01 PM, philipp jung <[email protected]> wrote: >> Hi, >> >> I tried rebuilding paraview with: make -B -dr -j 12 > stdout.txt 2> >> stderr.txt >> >> Unfortunately the problem still persists. The output file stderr.txt is >> attached, the other one is too large. >> >> >> Philipp >> >> On 19.01.2017 16:36, Utkarsh Ayachit wrote: >>> Also try running with command line argument "-dr" to see if that makes >>> any difference. >>> >>> On Thu, Jan 19, 2017 at 4:11 AM, philipp jung <[email protected]> >>> wrote: >>>> Hi, >>>> >>>> I tested the datasets on two different PCs at university and it did >>>> work. It seems to be a problem with paraview on my home computer. Also I >>>> could not use the feature with any datasets at home ( I tried >>>> .vtk,.vti,.csv files). I will try rebuilding paraview later today and >>>> report back. >>>> >>>> >>>> Philipp Jung >>>> >>>> On 18.01.2017 22:59, Utkarsh Ayachit wrote: >>>>> Can you share a sample dataset that reproduces the problem? That'll >>>>> make it easier to track it down. Thanks. >>>>> >>>>> Utkarsh >>>>> >>>>> On Tue, Jan 17, 2017 at 11:52 AM, philipp jung <[email protected]> >>>>> wrote: >>>>>> Dear Paraview Team, >>>>>> >>>>>> I am currently working on a custom plugin which returns Polydata with an >>>>>> attached UnsignedCharArray as respective categories for all points. I >>>>>> want to map these categories to colors using the "Interpret Values As >>>>>> Categories" feature. When I enable "Interpret Values As Categories" >>>>>> paraview immediately crashes with "Floating point exception (core >>>>>> dumped)" as console output. I tried using the feature with a couple >>>>>> other datasets (netCDF-format) and got the same result. >>>>>> >>>>>> I am using paraview version 5.2.0-RC3-22-g3fca33d 64bit on Ubuntu 16.04. >>>>>> >>>>>> >>>>>> Any indication what might be causing this behavior is much appreciated. >>>>>> >>>>>> >>>>>> Thank you very much. >>>>>> >>>>>> Philipp Jung >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
