py", line 254, in figureįile "/usr/lib/ pymodules/ python2.
![python 2.6.6 pylab xshell python 2.6.6 pylab xshell](https://www.codegrepper.com/codeimages/install-python-3.8-on-wsl.png)
py", line 276, in gcfįile "/usr/lib/ pymodules/ python2. py", line 582, in gcaįile "/usr/lib/ pymodules/ python2. py", line 2077, in pcolorįile "/usr/lib/ pymodules/ python2.
![python 2.6.6 pylab xshell python 2.6.6 pylab xshell](https://i.stack.imgur.com/LOK8u.png)
If I add this line after the imports, I get a new type of error :įile "/usr/lib/ pymodules/ python2. If I add : from import * at the top (before the other imports), the segfault reappears. The segfault disappears if I put the 3 OpenGL imports after the matplotlib import ! I was able to make a minimalist test case for this bug : #4 0x00007fffe81c8480 in method_ varargs_ call_handler () from /usr/lib/ pymodules/ python2. #3 0x00007fffe81e08a7 in Py::ExtensionMo dule ::invoke_ method_ varargs( std::basic_ string, std::allocator > const&, Py::Tuple const&) () from /usr/lib/ pymodules/ python2. #2 0x00007fffe81d58fb in _path_module: :update_ path_extents( Py::Tuple const&) () #1 0x00007fffe81cbaf4 in py_to_agg_ transformation_ matrix( _object*, bool) ()įrom /usr/lib/ pymodules/ python2. I have run the script through the GDB debugger, here is the complete log of the crash which may help us : It seems my version of matplotlib is a newer one : 0.99.3-1ubuntu1 (on ubuntu 10.10), which may be an explanation. The error is on line 229 in opengl.py (call to pcolor), but may be elsewhere, as segmentation faults can have multiple causes. If called through openfovea with a random AFM file, there is no error. There is a segmentation fault if you test fovea_toolbox/ opengl_ gtk.py through command line (with the test matrix).