Hi Mark,
Crashes that only occur in parallel can be hard to debug. The memory
inspector makes it easy to attach gdb to any of ParaView's processes.
After you've connected to the parallel pvserver, open the memory
inspector, right click on the process of interest, select remote
command. If your local then use local gdb template. There's a remote gdb
template to support remote debugging where the remote system provides
ssh access to compute nodes. It works for most clusters, I've never been
able to make it work the Cray. A second option is to pass --enable-bt
on the command line when you start pvserver. Again on Cray it's
problematic, but Cray provides it's own solution called ATP. You just
link against it and set their special environment variable when you
submit your job. All of these options require a Debug or RelWithDebInfo
build.
Hope this helps!
Burlen
On 3/22/2014 2:04 PM, Vanmoer, Mark W wrote:
Hi paraview,
I have a custom filter that takes two input connections and then uses
vtkIntegrateAttributes on both to find the ratio of their volumes.
This is output as an unstructured grid, following the example of
vtkIntegrateAttributes. The custom filter works fine in ParaView 4.0.1
when running as a single process. However, when I try to run on
multiple processes, it crashes the pvserver with
=====================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= EXIT CODE: 139
= CLEANING UP REMAINING PROCESSES
= YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
=====================================================================================
APPLICATION TERMINATED WITH THE EXIT STRING: Segmentation fault
(signal 11)
while in the client terminal I get dozens of errors relating to broken
pipes and not being able to send or receive tags (which I take as a
consequence of the pvserver crashing)
I see that vtkIntegrateAttributes uses vtkMultiProcessController.
Should I be using this class and implementing a SetController?
Thanks,
Mark
_______________________________________________
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
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/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
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
