Hi David,<br><br>I uncovered a new segfault. Admittedly this is a very strange case, but it used to work:<br><br><div style="margin-left: 40px;">import libvtkCoProcessorPython as cp<br>pipeline = cp.vtkCPPythonScriptPipeline()<br>
<br># crash here<br>import libvtkCommonPython<br></div><br>Run with vtkpython, or regular python. You might need to add /path/to/paraview-build/bin to sys.path. You get the vtkCoProcessorPython library if you build paraview with
python and PARAVIEW_ENABLE_COPROCESSING.<br><br>Here is what is happening- the ctor of vtkCPPythonScriptPipeline initializes paraview (vtkPVMain::Initialize), creates a vtkPVPythonInterpretor, and execs code in the new interpreter that imports vtk modules. If it makes any difference, the vtk that is imported is paraview/vtk/__init__.py, not the regular vtk/__init__.py. Note, it doesn't crash if I import libvtkFilteringPython, or any other kit, just vtkCommon. I guess because vtkCommon contains the specially wrapped vtkTimeStamp.<br>
<br><br><br>backtrace-<br><br>0x00007fffe43c6bfe in PyVTKSpecialType_New (newmethod=0x7fffe4a18180, methods=0x7fffe4a180e0, constructors=0x7fffe4a18140, <br>
classname=0x7fffe47a310e "vtkTimeStamp", docstring=0x7fffe4a181e0, smethods=0x7fffe4a181a0)<br> at /source/paraview/ParaView/VTK/Wrapping/Python/PyVTKSpecialObject.cxx:341<br>341 newmethod->ml_doc = PyString_AsString(info->docstring);<br>
<br>(gdb) bt<br>#0 0x00007fffe43c6bfe in PyVTKSpecialType_New (newmethod=0x7fffe4a18180, methods=0x7fffe4a180e0, constructors=0x7fffe4a18140, <br> classname=0x7fffe47a310e "vtkTimeStamp", docstring=0x7fffe4a181e0, smethods=0x7fffe4a181a0)<br>
at /source/paraview/ParaView/VTK/Wrapping/Python/PyVTKSpecialObject.cxx:341<br>#1 0x00007fffe46fbb4a in PyVTKClass_vtkTimeStampNew () at /source/paraview/build/VTK/Common/vtkTimeStampPython.cxx:164<br>#2 0x00007fffdd07cf4c in initlibvtkCommonPython () at /source/paraview/build/VTK/Common/vtkCommonPythonInit.cxx:1055<br>
#3 0x00000000004c081c in _PyImport_LoadDynamicModule ()<br>#4 0x00000000004bed93 in ?? ()<br>#5 0x00000000004bf00f in ?? ()<br>#6 0x00000000004bf6cb in ?? ()<br>#7 0x00000000004bfc14 in PyImport_ImportModuleLevel ()<br>
#8 0x00000000004a16ab in ?? ()<br>#9 0x000000000041f0c7 in PyObject_Call ()<br>#10 0x00000000004a226f in ?? ()<br>#11 0x00000000004a55fc in PyEval_EvalFrameEx ()<br>#12 0x00000000004a9671 in PyEval_EvalCodeEx ()<br>#13 0x00000000004a9742 in PyEval_EvalCode ()<br>
#14 0x00000000004c9a0e in PyRun_FileExFlags ()<br>#15 0x00000000004c9c24 in PyRun_SimpleFileExFlags ()<br>#16 0x000000000041a7ff in Py_Main ()<br><br><br><div class="gmail_quote">On Tue, Jul 6, 2010 at 9:51 AM, David Gobbi <span dir="ltr"><<a href="mailto:david.gobbi@gmail.com" target="_blank">david.gobbi@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi All,<br>
<br>
Another wrapping update was pushed this morning. This time, the<br>
parser and the wrappers have been updated so that they can build while<br>
ignoring the BTX/ETX markers in the header files. Here is a new CMake<br>
variable for people to play with:<br>
<br>
VTK_IGNORE_BTX "Ignore BTX and ETX in header files."<br>
<br>
If you turn this option ON, then the wrappers will parse the header<br>
files as if all the BTX/ETX markers had were removed, i.e. //BTX and<br>
//ETX will be treated as if they were just regular comments.<br>
<br>
Turning on this option will break any external wrapping, e.g. ParaView<br>
or Titan, because I do not yet export the hierarchy files. For now,<br>
it is just an experimental option for stand-alone VTK builds.<br>
<div><div></div><div><br>
David<br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
<br>
</div></div></blockquote></div><br>