[Paraview-developers] Segmentation fault: vtkEventQtSlotConnect (0xdea0f0): Cannot connect NULL objects

Michael Schlottke m.schlottke at aia.rwth-aachen.de
Wed Jun 5 16:39:04 EDT 2013


Hi Utkarsh,

your hunch was correct! It seems like an old ParaView-3.14 library directory was still in the LD_LIBRARY_PATH and caused mayhem during the startup phase. Once I removed that, everything seems to work just fine.

Thanks again for the advice

Michael

On Jun 5, 2013, at 14:10 , Utkarsh Ayachit wrote:

> Try running with LD_DEBUG set to libs
> (http://linux.die.net/man/8/ld-linux). That will print all libraries
> being loaded. I wonder if there's a mismatch somewhere.
> 
> Utkarsh
> 
> On Tue, Jun 4, 2013 at 9:59 AM, Michael Schlottke
> <m.schlottke at aia.rwth-aachen.de> wrote:
>> Hi there,
>> 
>> I know this issue has been on the list before (once in Oct '12 and then
>> again Jan '13), but it seemed like it was never fully (or at least publicly)
>> resolved. I seem to get the exact same error as the other user got back
>> then, after compiling and installing ParaView-4.0.0-RC2 on a Linux machine:
>> 
>> ###################################################
>> $> ./paraview
>> ERROR: In
>> /home/mic/.pool/.src/ParaView-4.0.0-RC2/VTK/GUISupport/Qt/vtkEventQtSlotConnect.cxx,
>> line 68
>> vtkEventQtSlotConnect (0xdea0f0): Cannot connect NULL objects.
>> 
>> Program received signal SIGSEGV, Segmentation fault.
>> ###################################################
>> 
>> I used gcc-4.8.0 as well as clang-3.3 to compile ParaView, and still get the
>> same error. Also, the same error whether I do it on a 2.6.34 or 3.1.10
>> kernel machine (openSUSE 11.3 and 12.1 respectively). The used Qt version is
>> 4.8.4 (also compiled with gcc and clang). I also tried Utkarsh's solution by
>> removing the $HOME/.config/ParaView directory, but to no avail. Starting
>> paraview with the '-dr' option doesn't change anything either. When I try to
>> run a previously compiled ParaView 3.14.1 client, it works without a glitch.
>> 
>> I recompiled ParaView for a Debug build and used gdb to get a stack trace:
>> 
>> ###################################################
>> 0x00007ffff6962720 in pqApplicationCore::settings (this=0xb7f360) at
>> /home/mic/.pool/.src/ParaView-4.0.0-RC2/Qt/Core/pqApplicationCore.cxx:635
>> 635      vtkProcessModule::GetProcessModule()->GetOptions());
>> (gdb) where
>> #0  0x00007ffff6962720 in pqApplicationCore::settings (this=0xb7f360) at
>> /home/mic/.pool/.src/ParaView-4.0.0-RC2/Qt/Core/pqApplicationCore.cxx:635
>> #1  0x00007ffff69e55e8 in pqOutputWindow::showEvent (this=0xb6c290,
>> e=0x7fffffffc820) at
>> /home/mic/.pool/.src/ParaView-4.0.0-RC2/Qt/Core/pqOutputWindow.cxx:200
>> #2  0x00007fffdc3d5027 in QWidget::event(QEvent*) () from
>> /home/mic/.pool/qt-4.8.4_clang/lib/libQtGui.so.4
>> #3  0x00007fffdc3899f6 in QApplicationPrivate::notify_helper(QObject*,
>> QEvent*) () from /home/mic/.pool/qt-4.8.4_clang/lib/libQtGui.so.4
>> #4  0x00007fffdc38c70e in QApplication::notify(QObject*, QEvent*) () from
>> /home/mic/.pool/qt-4.8.4_clang/lib/libQtGui.so.4
>> #5  0x00007fffdbab2896 in QCoreApplication::notifyInternal(QObject*,
>> QEvent*) () from /home/mic/.pool/qt-4.8.4_clang/lib/libQtCore.so.4
>> #6  0x00007fffdc3d3b4c in QWidgetPrivate::show_helper() () from
>> /home/mic/.pool/qt-4.8.4_clang/lib/libQtGui.so.4
>> #7  0x00007fffdc3d4646 in QWidget::setVisible(bool) () from
>> /home/mic/.pool/qt-4.8.4_clang/lib/libQtGui.so.4
>> #8  0x00007fffdc84c9d0 in QDialog::setVisible(bool) () from
>> /home/mic/.pool/qt-4.8.4_clang/lib/libQtGui.so.4
>> #9  0x00007ffff696648b in QWidget::show (this=0xb6c290) at
>> /home/mic/.pool/qt-4.8.4_clang/include/QtGui/qwidget.h:494
>> #10 0x00007ffff69e5421 in pqOutputWindow::onDisplayErrorText (this=0xb6c290,
>> text=...) at
>> /home/mic/.pool/.src/ParaView-4.0.0-RC2/Qt/Core/pqOutputWindow.cxx:174
>> #11 0x00007ffff6a72db2 in pqOutputWindow::qt_static_metacall (_o=0xb6c290,
>> _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fffffffcbc0) at
>> /home/mic/.pool/.build/ParaView-4.0.0-RC2_debug/Qt/Core/moc_pqOutputWindow.cxx:64
>> #12 0x00007fffdbac9a30 in QMetaObject::activate(QObject*, QMetaObject
>> const*, int, void**) () from
>> /home/mic/.pool/qt-4.8.4_clang/lib/libQtCore.so.4
>> #13 0x00007ffff6a7248f in pqOutputWindowAdapter::displayErrorText
>> (this=0xb6c3e0, _t1=...) at
>> /home/mic/.pool/.build/ParaView-4.0.0-RC2_debug/Qt/Core/moc_pqOutputWindowAdapter.cxx:122
>> #14 0x00007ffff69e39ce in pqOutputWindowAdapter::DisplayErrorText
>> (this=0xb6c3e0, text=0xc62e30 "ERROR: In
>> /home/mic/.pool/.src/ParaView-4.0.0-RC2/VTK/GUISupport/Qt/vtkEventQtSlotConnect.cxx,
>> line 68\nvtkEventQtSlotConnect (0xdea0f0): Cannot connect NULL
>> objects.\n\n")
>>    at
>> /home/mic/.pool/.src/ParaView-4.0.0-RC2/Qt/Core/pqOutputWindowAdapter.cxx:109
>> #15 0x00007ffff69e3a4f in non-virtual thunk to
>> pqOutputWindowAdapter::DisplayErrorText(char const*) (this=0xb6c3f0,
>>    text=0xc62e30 "ERROR: In
>> /home/mic/.pool/.src/ParaView-4.0.0-RC2/VTK/GUISupport/Qt/vtkEventQtSlotConnect.cxx,
>> line 68\nvtkEventQtSlotConnect (0xdea0f0): Cannot connect NULL
>> objects.\n\n")
>>    at
>> /home/mic/.pool/.src/ParaView-4.0.0-RC2/Qt/Core/pqOutputWindowAdapter.cxx:111
>> #16 0x00007fffdb112acc in vtkOutputWindowDisplayErrorText (message=0xc62e30
>> "ERROR: In
>> /home/mic/.pool/.src/ParaView-4.0.0-RC2/VTK/GUISupport/Qt/vtkEventQtSlotConnect.cxx,
>> line 68\nvtkEventQtSlotConnect (0xdea0f0): Cannot connect NULL
>> objects.\n\n")
>>    at
>> /home/mic/.pool/.src/ParaView-4.0.0-RC2/VTK/Common/Core/vtkOutputWindow.cxx:41
>> #17 0x00007fffe3db6f61 in vtkEventQtSlotConnect::Connect (this=0xdea0f0,
>> vtk_obj=0x0, event=66, qt_obj=0xf57c60, slot=0x7ffff6b04e00
>> "1connectionCreated(vtkObject*, unsigned long, void*, void*)",
>> client_data=0x0, priority=0, type=Qt::AutoConnection)
>>    at
>> /home/mic/.pool/.src/ParaView-4.0.0-RC2/VTK/GUISupport/Qt/vtkEventQtSlotConnect.cxx:68
>> #18 0x00007ffff6a3af74 in pqServerManagerObserver::pqServerManagerObserver
>> (this=0xf57c60, p=0xb7f360) at
>> /home/mic/.pool/.src/ParaView-4.0.0-RC2/Qt/Core/pqServerManagerObserver.cxx:73
>> #19 0x00007ffff6960b6d in pqApplicationCore::constructor (this=0xb7f360) at
>> /home/mic/.pool/.src/ParaView-4.0.0-RC2/Qt/Core/pqApplicationCore.cxx:155
>> #20 0x00007ffff69606f8 in pqApplicationCore::pqApplicationCore
>> (this=0xb7f360, argc=@0x7fffffffd4fc: 1, argv=0x7fffffffd6b8,
>> options=0xb155e0, parentObject=0x0) at
>> /home/mic/.pool/.src/ParaView-4.0.0-RC2/Qt/Core/pqApplicationCore.cxx:132
>> #21 0x00007ffff7b505f1 in pqPVApplicationCore::pqPVApplicationCore
>> (this=0xb7f360, argc=@0x7fffffffd4fc: 1, argv=0x7fffffffd6b8, options=0x0)
>> at
>> /home/mic/.pool/.src/ParaView-4.0.0-RC2/Qt/ApplicationComponents/pqPVApplicationCore.cxx:68
>> #22 0x0000000000409c52 in pqparaviewInitializer::Initialize
>> (this=0x7fffffffd570, argc=1, argv=0x7fffffffd6b8) at
>> /home/mic/.pool/.build/ParaView-4.0.0-RC2_debug/Applications/ParaView/pqparaviewInitializer.cxx:78
>> #23 0x00000000004098d1 in main (argc=1, argv=0x7fffffffd6b8) at
>> /home/mic/.pool/.build/ParaView-4.0.0-RC2_debug/Applications/ParaView/paraview_main.cxx:76
>> ###################################################
>> 
>> Is there any new knowledge on what this might be related to or how I can fix
>> this?
>> 
>> Regards,
>> 
>> Michael
>> 
>> 
>> --
>> Michael Schlottke
>> 
>> SimLab Highly Scalable Fluids & Solids Engineering
>> Jülich Aachen Research Alliance (JARA-HPC)
>> RWTH Aachen University
>> Wüllnerstraße 5a
>> 52062 Aachen
>> Germany
>> 
>> Phone: +49 (241) 80 95188
>> Fax: +49 (241) 80 92257
>> Mail: m.schlottke at aia.rwth-aachen.de
>> Web: http://www.jara.org/jara-hpc
>> 
>> 
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2308 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20130605/a93c8b2f/attachment.bin>


More information about the Paraview-developers mailing list