Here is a wild guess: the segfaults are from tests that call vtkRenderWindowInteractor::New(), causing an infinite loop inside vtkGraphicsFactory.cxx when compiled with VTK_USE_OSMESA. I'm on vacation right now and can't verify any of this, I shouldn't even be on email...<br>
<br>Pat<br><br><div class="gmail_quote">On Sun, Mar 7, 2010 at 2:08 PM, Burlen Loring <span dir="ltr"><<a href="mailto:burlen.loring@gmail.com">burlen.loring@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi John,<br>
<br>
Can you run one of the tests in a debugger and see specifically where it segfaults? I'm sure that will give you the clue you're after. I guess this is obvious so maybe there is a reason you haven't done it.<br>
<font color="#888888">
<br>
Burlen</font><div><div></div><div class="h5"><br>
<br>
Biddiscombe, John A. wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Dear Anyone,<br>
<br>
After much head scratching and recomiling hundreds of times with different options, I'm still no closer to solving an issue (Any many many thanks to Pat who's instructions I've been following, but I still get the same segfaults as when I did it myself using a slightly less 'strict' procedure).<br>
<a href="http://cdash.cscs.ch/index.php?project=pv-meshless&date=2010-03-06" target="_blank">http://cdash.cscs.ch/index.php?project=pv-meshless&date=2010-03-06</a><br>
Top dashboard from Cray Compute node linux<br>
Faill =414 Pass = 325<br>
<br>
I don't know why these tests are all segfaulting (a few fail, that's ok, fail is alright, but segfaults I want to knwo why). Does anyone know what theses ones do that the others do not. Is one library in particular called in these tests that the others do not?<br>
<br>
Any clues gratefully accepted<br>
<br>
BIG NOTE : when ctest runs, I'm using an interactive login node, so tests which use MPI are being started with "aprun program" and are run on a compute node (some even pass).<br>
Tests which do not use MPI are being run on the login/service node - they have the same CPUs etc, so all should be well, but it's a clue anyway (however some of these pass too, so not a very good clue).<br>
<br>
Thanks<br>
<br>
JB<br>
_______________________________________________<br>
Paraview-developers mailing list<br>
<a href="mailto:Paraview-developers@paraview.org" target="_blank">Paraview-developers@paraview.org</a><br>
<a href="http://public.kitware.com/mailman/listinfo/paraview-developers" target="_blank">http://public.kitware.com/mailman/listinfo/paraview-developers</a><br>
<br>
</blockquote>
<br>
_______________________________________________<br>
Paraview-developers mailing list<br>
<a href="mailto:Paraview-developers@paraview.org" target="_blank">Paraview-developers@paraview.org</a><br>
<a href="http://public.kitware.com/mailman/listinfo/paraview-developers" target="_blank">http://public.kitware.com/mailman/listinfo/paraview-developers</a><br>
</div></div></blockquote></div><br>