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