[Paraview] versions > 2.4 crashing painfully
Dominik Szczerba
domi at vision.ee.ethz.ch
Wed Feb 7 12:51:08 EST 2007
I have renamed the dri kernel module and PV 2.9 works, only unusably
slow. So the error is in combination PV-dri. The problem is not there
with version 2.4 nor with the latest VTK.
Dominik Szczerba, Ph.D.
Computer Vision Lab CH-8092 Zurich
http://www.vision.ee.ethz.ch/~domi
Berk Geveci wrote:
> I cannot reproduce this. I tried the binaries on multiple GNU/Linux
> boxes (Debian, Red Hat 32 and 64 bit) with different OpenGL drivers
> (Mesa and multiple version of nVidia) and on Windows. Also, the output
> of valgrind that you posted seems to point to some OpenGL driver issues.
>
> -berk
>
> On 2/7/07, *Dominik Szczerba* <domi at vision.ee.ethz.ch
> <mailto:domi at vision.ee.ethz.ch>> wrote:
>
> This is a nasty devil, the log below.
>
>
>
> ==20598== Memcheck, a memory error detector.
> ==20598== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward
> et al.
> ==20598== Using LibVEX rev 1658, a library for dynamic binary
> translation.
> ==20598== Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP.
> ==20598== Using valgrind-3.2.1-Debian, a dynamic binary instrumentation
> framework.
> ==20598== Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward
> et al.
> ==20598== For more details, rerun with: -v
> ==20598==
> libGL: XF86DRIGetClientDriverName: 1.7.2 i915 (screen 0)
> libGL: OpenDriver: trying /usr/lib/dri/i915_dri.so
> drmOpenByBusid: Searching for BusID pci:0000:00: 02.0
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 9, (OK)
> drmOpenByBusid: drmOpenMinor returns 9
> drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
> libGL error:
> Can't open configuration file /etc/drirc: No such file or directory.
> libGL error:
> Can't open configuration file /etc/drirc: No such file or directory.
> libGL: XF86DRIGetClientDriverName: 1.7.2 i915 (screen 0)
> drmOpenByBusid: Searching for BusID pci:0000:00:02.0
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 11, (OK)
> drmOpenByBusid: drmOpenMinor returns 11
> drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
> libGL error:
> Can't open configuration file /etc/drirc: No such file or directory.
> Segmentation fault
>
>
> Dominik Szczerba, Ph.D.
> Computer Vision Lab CH-8092 Zurich
> http://www.vision.ee.ethz.ch/~domi
>
>
> Berk Geveci wrote:
> > There should be some sort of stack even if Qt and VTK are not
> compiled
> > with debug. However, I am confused, how can paraview be compiled debug
> > and VTK not?
> > I am guessing whatever is causing the crash is corrupting the stack
> > also. Can you try to run in valgrind? I believe valgrind is a debian
> > package also so getting it should be easy. Once you get it, simply run
> > valgrind /path/to/paraview_alpha > log.txt
> >
> > -berk
> >
> > On 2/6/07, *Dominik Szczerba* < domi at vision.ee.ethz.ch
> <mailto:domi at vision.ee.ethz.ch>
> > <mailto:domi at vision.ee.ethz.ch <mailto:domi at vision.ee.ethz.ch>>>
> wrote:
> >
> > I have compiled PV 2.9 alpha with -g (CMAKE_BUILD_TYPE debug)
> which I
> > confirmed by make VERBOSE=1. I run PV in gdb, it crashes on a
> file load,
> > with NO stack:
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > Cannot remove breakpoints because program is no longer writable.
> > It might be running in another process.
> > Further execution is probably impossible.
> > 0xb1d511f0 in ?? ()
> > (gdb)
> > (gdb)
> > (gdb) bt
> > #0 0xb1d511f0 in ?? ()
> > #1 0xb4c2ad1c in ?? ()
> > #2 0x08095048 in ?? ()
> > #3 0x00000000 in ?? ()
> >
> > My guess is I should use debug versions of QT and VTK too, but
> I didnt
> > see such configure options..?
> >
> > --ds
> >
> > Dominik Szczerba, Ph.D.
> > Computer Vision Lab CH-8092 Zurich
> > http://www.vision.ee.ethz.ch/~domi
> >
> >
> > Berk Geveci wrote:
> > > The first thing to do would be to try to find a reproducible
> case
> > when
> > > it crashes. If that doesn't work, try running a debug build
> in a
> > > debugger trying to get a stack trace. I will run in valgrind to
> > see if I
> > > can catch anything.
> > >
> > > -berk
> > >
> > > On 2/6/07, *Dominik Szczerba* < domi at vision.ee.ethz.ch
> <mailto:domi at vision.ee.ethz.ch>
> > <mailto:domi at vision.ee.ethz.ch <mailto:domi at vision.ee.ethz.ch>>
> > > <mailto: domi at vision.ee.ethz.ch
> <mailto:domi at vision.ee.ethz.ch> <mailto:domi at vision.ee.ethz.ch
> <mailto:domi at vision.ee.ethz.ch>>>>
> > wrote:
> > >
> > > Both 2.6 and 2.9 crash after some short activity. 2.9
> > unpredictably
> > > (would open some files), 2.6 on most of my VTK files 2.4
> opens
> > without
> > > problems. Where should I look?
> > >
> > >
> > > Dominik Szczerba, Ph.D.
> > > Computer Vision Lab CH-8092 Zurich
> > > http://www.vision.ee.ethz.ch/~domi
> > >
> > >
> > > Berk Geveci wrote:
> > > > I have been using ParaView 2.6 and 2.9 on Linux, OS X and
> > Window XP
> > > > without any serious stability problems. Does it crash
> at startup
> > > or when
> > > > you are doing anything specific?
> > > >
> > > > -berk
> > > >
> > > > On 2/6/07, *Dominik Szczerba* < domi at vision.ee.ethz.ch
> <mailto:domi at vision.ee.ethz.ch>
> > <mailto:domi at vision.ee.ethz.ch <mailto:domi at vision.ee.ethz.ch>>
> > > <mailto: domi at vision.ee.ethz.ch
> <mailto:domi at vision.ee.ethz.ch> <mailto:domi at vision.ee.ethz.ch
> <mailto:domi at vision.ee.ethz.ch>>>
> > > > <mailto: domi at vision.ee.ethz.ch
> <mailto:domi at vision.ee.ethz.ch>
> > <mailto:domi at vision.ee.ethz.ch
> <mailto:domi at vision.ee.ethz.ch>> <mailto:domi at vision.ee.ethz.ch
> <mailto:domi at vision.ee.ethz.ch>
> > <mailto: domi at vision.ee.ethz.ch
> <mailto:domi at vision.ee.ethz.ch>>>>>
> > > wrote:
> > > >
> > > > Hi,
> > > > >From PV 2.6, including PV 2.9.x I have been
> experiencing
> > > crashes within
> > > > seconds of operation. Have I missed anything obvious
> > recently?
> > > Version
> > > > 2.4.x works stable as rock. I tried compiling the
> latest
> > 2.9 beta
> > > > myself
> > > > and it crashes all the same as the precompiled
> version. I
> > > would be glad
> > > > to investigate the problem (debian/unstable).
> > > > PS. I have no problems at all with the latest VTK.
> > > > thanks,
> > > > Dominik
> > > > _______________________________________________
> > > > ParaView mailing list
> > > > ParaView at paraview.org
> <mailto:ParaView at paraview.org> <mailto:ParaView at paraview.org
> <mailto:ParaView at paraview.org> >
> > <mailto:ParaView at paraview.org <mailto:ParaView at paraview.org>
> <mailto:ParaView at paraview.org <mailto:ParaView at paraview.org>>>
> > > <mailto: ParaView at paraview.org
> <mailto:ParaView at paraview.org> <mailto:ParaView at paraview.org
> <mailto:ParaView at paraview.org>>
> > <mailto: ParaView at paraview.org <mailto:ParaView at paraview.org>
> <mailto: ParaView at paraview.org <mailto:ParaView at paraview.org>>>>
> > > > http://www.paraview.org/mailman/listinfo/paraview
> > > < http://www.paraview.org/mailman/listinfo/paraview>
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Berk Geveci
> > > > Kitware Inc.
> > > > 28 Corporate Drive
> > > > Clifton Park, NY, 12065
> > >
> > >
> > >
> > >
> > > --
> > > Berk Geveci
> > > Kitware Inc.
> > > 28 Corporate Drive
> > > Clifton Park, NY, 12065
> >
> >
> >
> >
> > --
> > Berk Geveci
> > Kitware Inc.
> > 28 Corporate Drive
> > Clifton Park, NY, 12065
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org <mailto:ParaView at paraview.org>
> http://www.paraview.org/mailman/listinfo/paraview
>
>
>
>
> --
> Berk Geveci
> Kitware Inc.
> 28 Corporate Drive
> Clifton Park, NY, 12065
More information about the ParaView
mailing list