I'm fairly sure this is a Sun OpenGl problem. I could not get anything out of glGetError - simply making the call caused X to crash. However, the X error handler gets a GLXBadDrawable.
I have found that modifying a simple OpenGl program to give an invalid call to glXMakeCurrent will have the same effect. (eg. glXMakeCurrent(dpy,NULL,context)). I'm going to approach Sun and see what they say. John > >John D Stark: > |but when run remotely on another system ( linux / sgi / sun ), with the > |display set to my machine OpenDx causes the Xserver (Xsun) to crash when > |exiting. >... > |this may be a Sun OpenGL bug. > >Could be. I've run remote SGI->SGI, SGI->FreeBSD/Linux with no probs. >But not ->Sun IIRC. > > |A temporary and not very pleasant solution has been to add the lines: > | B_result = glXMakeCurrent (DPY, XWINID, OGLCTX); > | if(!B_result) exit(0); >... > |I'm using opendx 4.4.0 form the tar.gz archive. > >Would be interesting to see what glGetError has to say just before you >exit. See Ch14 in the Red Book for a code sample >(http://www.lcg.ufrj.br/compgraf1/downloads/OpenGL_Programming_Guide/chapter14. html). > >For full effect you may want to set your own X error handler just before >glXMakeCurrent with XSetErrorHandler to catch things like GLXBadDrawable, >etc. to see what GLX isn't happy about. > >Randy > >-- >Randall Hopper (mailto:[EMAIL PROTECTED]) >Lockheed Martin Operation Support >EPA Scientific Visualization Center >US EPA N127-01; RTP, NC 27711 ------------------------------------------ John Stark Applications Programmer Southampton Oceanography Centre Tel. +44 (0)23 8059 6571 e-mail [EMAIL PROTECTED] ------------------------------------------
