I think I have a very recent version of the driver (as I updated to the last
kubuntu release 9.10 karmic koala and I maintain it up-to-date quite often).
In fact I wonder if some thing changed in the new Intel's driver. Indeed,
before I upgraded ubuntu, I could run pythonOcc without any problem of such
kind.
 Maybe I just need to recompile OpenCascade (but this would be quite
unconvenient if I have to do this each time I update the Intels driver and
anyway it does not make much sens to me). I'll check when back home.

Loïc


On Mon, Dec 7, 2009 at 6:34 AM, Thomas Paviot <tpav...@gmail.com> wrote:

> Hi Loïc,
>
> This issue seems related to your video card driver. I browsed the OCC forum
> and found this thread: http://www.opencascade.org/org/forum/thread_14229/.
> Paul Jimenez points out that "Intel's OpenGL implementation seems to be
> problematic with OpenCascade."
>
> Be sure you use the latest version of the driver.
>
> Cheers,
>
> Thomas
>
> 2009/12/6 Simon Loic <simon1l...@gmail.com>
>
> I checked at home I still have this segmentation fault. I'm wondering if
>> it's not a bug in the intel driver. If you have any suggestions?
>>
>>
>> >> python Level1/Geometry/geometry_demos.py
>> Here is the backtrace:
>>
>> """
>> #0  0xb182d7c0 in intel_region_buffer () from /usr/lib/dri/i965_dri.so
>> #1  0xb181e545 in intelClearWithBlit () from /usr/lib/dri/i965_dri.so
>> #2  0xb1821f77 in ?? () from /usr/lib/dri/i965_dri.so
>> #3  0xb1895b9c in _mesa_Clear () from /usr/lib/dri/i965_dri.so
>> #4  0x06f28343 in TelInitWS () from
>> /opt/OpenCASCADE6.3.0/lib/libTKOpenGl.so.0
>> #5  0x06f25d40 in call_subr_open_ws () from
>> /opt/OpenCASCADE6.3.0/lib/libTKOpenGl.so.0
>> #6  0x06f357be in call_togl_view () from
>> /opt/OpenCASCADE6.3.0/lib/libTKOpenGl.so.0
>> #7  0x06eeb7cd in OpenGl_GraphicDriver::View(CALL_DEF_VIEW&)
>> ()
>>    from
>> /opt/OpenCASCADE6.3.0/lib/libTKOpenGl.so.0
>>
>> #8  0x039794ce in Visual3d_View::SetWindow(Handle_Aspect_Window const&)
>> ()
>>    from
>> /opt/OpenCASCADE6.3.0/lib/libTKV3d.so.0
>>
>> #9  0x0396106c in V3d_View::SetWindow(Handle_Aspect_Window const&)
>> ()
>>    from
>> /opt/OpenCASCADE6.3.0/lib/libTKV3d.so.0
>>
>> #10 0x0457a62d in Display3d::Init(int)
>> ()
>> ---Type <return> to continue, or q <return> to
>> quit---
>>    from /usr/local/lib/python2.6/dist-packages/OCC/_Visualization.so
>> #11 0x04579641 in _wrap_Display3d_Init ()
>>    from /usr/local/lib/python2.6/dist-packages/OCC/_Visualization.so
>> #12 0x080dcdc1 in PyEval_EvalFrameEx ()
>> #13 0x080dd384 in PyEval_EvalFrameEx ()
>> #14 0x080dd384 in PyEval_EvalFrameEx ()
>> #15 0x080dddf2 in PyEval_EvalCodeEx ()
>> #16 0x080dc1b4 in PyEval_EvalFrameEx ()
>> #17 0x080dddf2 in PyEval_EvalCodeEx ()
>> #18 0x080ddef7 in PyEval_EvalCode ()
>> #19 0x080faa1f in PyRun_FileExFlags ()
>> #20 0x080fac12 in PyRun_SimpleFileExFlags ()
>> #21 0x0805c8d8 in Py_Main ()
>> #22 0x0805baeb in main ()
>> """
>>
>> Loïc
>>
>>
>> On Thu, Dec 3, 2009 at 10:46 AM, Simon Loic <simon1l...@gmail.com> wrote:
>>
>>> Thanks Thomas,
>>> I updated your latest commit, and launched the samples you updated
>>> (Level1/Geometry/geometry_demos.py and
>>> Level1/TopologyBuilding/topology_building.py - I don't have smesh so far) .
>>> Unfortunately they both end with a seg fault after the viewer is created.
>>>
>>> Here is the output.
>>> """
>>> Display3d class initialization starting ...
>>> Graphic device created.
>>> Xw_Window created.
>>> Viewer created.
>>> zsh: segmentation fault  python Level1/Geometry/geometry_demos.py
>>> """
>>> I'll try to investigate further on later.
>>>
>>> Loïc
>>>
>>>
>>> On Thu, Dec 3, 2009 at 5:18 AM, Thomas Paviot <tpav...@gmail.com> wrote:
>>>
>>>> Hi Loïc,
>>>>
>>>> The SmpleGui.py module is an improvement over the previous wxSamplesGui
>>>> that enables multiple graphical backends. For instance, if you decide
>>>> whether to use SimpleGui to manage the display, you first have to set the
>>>> graphical backend to use. Fos instance:
>>>>
>>>> set_backend('wx') #if you want to use wxPython
>>>> set_backend('qt') #if you want to use pyQt
>>>> set_backend('X') #if you want to use python-xlib (Linux/MacOSX up to
>>>> SL64bit)
>>>>
>>>> All the samples are not sync yet with the newest developments I made. In
>>>> ordrer to make the scripts work, you first have to insert the 2 lines:
>>>>
>>>> from OCC.Display.SimpleGui import *
>>>>
>>>> display, start_display, add_menu, add_function_to_menu = init_display()
>>>>
>>>> The graphical backend used by default will be the one available on your
>>>> machine. If you have both wxPython, PyQt and python-xlib installed, then 
>>>> the
>>>> default one will bis 'wx'.
>>>>
>>>> Best,
>>>>
>>>> Thomas
>>>>
>>>> 2009/12/2 Simon Loic <simon1l...@gmail.com>
>>>>
>>>>> Hi thomas,
>>>>> I've seen that you made a many commits recently relative to SimpleGUI,
>>>>> I have updated pythonOcc trunk to the last revision. It seems that many
>>>>> samples have don't work anymore.
>>>>> To be accurate if for example I call
>>>>> >>python Level2/PAF/test_box.py
>>>>> it wil throw me
>>>>> ""
>>>>> from OCC.Display.SimpleGui import start_display, display
>>>>> ImportError: cannot import name start_display
>>>>> ""
>>>>> the same for Level1/Mesh/simple_mesh.py Level1/Animation/animation.py
>>>>> and I guess many others (didn't try all of them).
>>>>>
>>>>> I also have a related problem with other scripts like
>>>>> Level1/Dimensions/dimensions.py where there si first a statement:
>>>>> >> from OCC.Display.SimpleGui import *
>>>>> and then at some point
>>>>> >> display.Context.Display(ais7.GetHandle())
>>>>> Then I get the following error:
>>>>> ""NameError: name 'display' is not defined""
>>>>>
>>>>> Are the samples uptodate and I simply did something wrong?
>>>>> Cheers,
>>>>> Loïc
>>>>>
>>>>> _______________________________________________
>>>>> Pythonocc-users mailing list
>>>>> Pythonocc-users@gna.org
>>>>> https://mail.gna.org/listinfo/pythonocc-users
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Pythonocc-users mailing list
>>>> Pythonocc-users@gna.org
>>>> https://mail.gna.org/listinfo/pythonocc-users
>>>>
>>>>
>>>
>>
>> _______________________________________________
>> Pythonocc-users mailing list
>> Pythonocc-users@gna.org
>> https://mail.gna.org/listinfo/pythonocc-users
>>
>>
>
> _______________________________________________
> Pythonocc-users mailing list
> Pythonocc-users@gna.org
> https://mail.gna.org/listinfo/pythonocc-users
>
>
_______________________________________________
Pythonocc-users mailing list
Pythonocc-users@gna.org
https://mail.gna.org/listinfo/pythonocc-users

Reply via email to