[Python-talk] How do I approach this? GLXBadContext

bruce.labitt at autoliv.com bruce.labitt at autoliv.com
Fri Jul 31 11:46:48 EDT 2009


Thanks to the suggestions of multiple list members I have put together a 
nice wxPython GUI that does most of what I need. 

The GUI allows the selection of various options, updates textboxes, etc. 
OnOK, the program either 1) Calculates and stores stimulus waveform(s), 
2)Plots a pre-existing datafile (which you can navigate to) or 3) 
Calculates and stores the stimulus, attaches to the ComputationEngine via 
ssh, computes the results, and plots the resultant datafile using mayavi2. 
 Very cool!

There are of course a few bugs, and things to work through.  (Bugs never 
sleep...  and they never go away by themselves...)  Most of the bugs have 
straight forward solutions - I just have to test enough to find and 
identify them.  Is there a systematic way of doing this?

One problem that is facing me is that I am getting a Segmentation Fault 
when executing Option 3).  The seg fault occurs just after the mayavi plot 
window pops up and some of the plot is rendered.  The error is:

The program 'python' received an X Window System Error.
This probably reflects a bug in the program.
The error was 'GLXBadContext'.
        (Details: serial 513275 error_code 177 request_code 161 minor_code 
5)
        (Note to programmers: normally, X errors are reported 
asynchronously;
        that is, you will receive an error a while after causing it.
        To debug your program, run it with the --sync command line
        option to change this behavior.  You can then get a meaningful
        backtrace from your debugger if you break on the gdk_x_error() 
function.)
Segmentation fault

How to start?  Ipython does not have a --sync option, nor does python... 
Is this a C(++) option?
Should I forward this to the mayavi (Enthought-dev) list?

One thing that I have in the shebang line is:
# !/usr/bin/env python

I use Ipython to run my app.  Is the shebang line ok for this?  Or should 
I change it.

Any tips on the GLXBadContext error would be greatly appreciated. 

The seg fault does not occur when I just use option 2).  The mayavi window 
pops up and plots the waveform.

Thanks!
Bruce


Bruce Labitt
Autoliv Electronics
1011B Pawtucket Blvd, PO Box 1858
Lowell, MA  01853

Email: bruce.labitt at autoliv.com. 
Tel:  (978) 674-6526
Fax: (978) 674-6581 

******************************
Neither the footer nor anything else in this E-mail is intended to or constitutes an <br>electronic signature and/or legally binding agreement in the absence of an <br>express statement or Autoliv policy and/or procedure to the contrary.<br>This E-mail and any attachments hereto are Autoliv property and may contain legally <br>privileged, confidential and/or proprietary information.<br>The recipient of this E-mail is prohibited from distributing, copying, forwarding or in any way <br>disseminating any material contained within this E-mail without prior written <br>permission from the author. If you receive this E-mail in error, please <br>immediately notify the author and delete this E-mail.  Autoliv disclaims all <br>responsibility and liability for the consequences of any person who fails to <br>abide by the terms herein. <br>
******************************


More information about the Python-talk mailing list