dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

On Tue, Oct 20, 2009 at 03:46:36PM -0400, Shawn Walker wrote:
>
> Hello.  This really isn't a bug, but I think it should not give such a
> ridiculous error.
>
> If I login to my linux machine and run the Stokes DEMO, I get this:
>
> ===================================
> Solving linear variational problem
>    Matrix of size 25140 x 25140 has 730140 nonzero entries.
>    Applying boundary conditions to linear system.
>    Applying boundary conditions to linear system.
>    Applying boundary conditions to linear system.
>    Solving linear system of size 25140 x 25140 (PETSc LU solver, umfpack).
> Plotting x (unnamed data), press 'q' to continue...
> ERROR: In /home/walker/src/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
> 344
> vtkXOpenGLRenderWindow (0xf083900): bad X server connection.
> DISPLAY=ERROR: In
> /home/walker/src/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 344
> vtkXOpenGLRenderWindow (0xf083900): bad X server connection.
> DISPLAY=ERROR: In
> /home/walker/src/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 344
> vtkXOpenGLRenderWindow (0xf083900): bad X server connection.
> DISPLAY=[0]PETSC ERROR:
> ------------------------------------------------------------------------
> [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation,
> probably memory access out of range
> [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
> [0]PETSC ERROR: or see
> http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSC
> ERROR: or try http://valgrind.org on linux or man libgmalloc on Apple to
> find memory corruption errors
> [0]PETSC ERROR: likely location of problem given in stack below
> [0]PETSC ERROR: ---------------------  Stack Frames
> ------------------------------------
> [0]PETSC ERROR: Note: The EXACT line numbers in the stack are not
> available,
> [0]PETSC ERROR:       INSTEAD the line number of the start of the function
> [0]PETSC ERROR:       is given.
> [0]PETSC ERROR: --------------------- Error Message
> ------------------------------------
> [0]PETSC ERROR: Signal received!
> [0]PETSC ERROR:
> ------------------------------------------------------------------------
> [0]PETSC ERROR: Petsc Release Version 3.0.0, Patch 8, Fri Aug 21 14:02:12
> CDT 2009
> [0]PETSC ERROR: See docs/changes/index.html for recent updates.
> [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting.
> [0]PETSC ERROR: See docs/index.html for manual pages.
>
> ========================================
>
> If I run it on the actual linux box, then there is no problem.  The reason
> it doesn't work in the other case is that there is no display (duh).   Is
> there a way to make dolfin just output a message if there is no display,
> instead of that giant error message?

It might be possible to detect this in Viper. What does Ola think?

In the meantime, try setting the environment variable DOLFIN_NOPLOT to
disable plotting:

  export DOLFIN_NOPLOT=1

--
Anders

Attachment: signature.asc
Description: Digital signature