On 12/03/2009 09:18 PM, Ian Romanick wrote: >> It was another suggestion in the GLEW thread - that the graphic context >> might be invalid. The application does have checks for this, but I'll >> try to reconfirm with the user that this is not the case. >> > This is easy enough to test. Run the app in a debugger. When it > faults, call glXGetCurrentContext. If it returns NULL, there's no > context bound in the current thread. > I have a report from the user.
(gdb) run Starting program: /usr/bin/toped warning: .dynamic section for "/lib/libresolv.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations [Thread debugging using libthread_db enabled] warning: .dynamic section for "/usr/lib/libcanberra-gtk.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libcanberra.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libltdl.so.7" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations Missing separate debuginfo for /usr/lib/libtdb.so.1 Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/a9/d89f5a179340f6dc46499bbcdce21d2f85a644.debug warning: .dynamic section for "/usr/lib/libfam.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations Program received signal SIGSEGV, Segmentation fault. 0x00000000 in ?? () Missing separate debuginfos, use: debuginfo-install GConf2-2.28.0-2.fc12.i686 ORBit2-2.14.17-3.fc12.i686 PackageKit-gtk-module-0.5.4-0.4.20091029git.fc12.i686 SDL-1.2.13-10.fc12.i686 atk-1.28.0-1.fc12.i686 cairo-1.8.8-3.fc12.i686 dbus-glib-0.82-2.fc12.i686 dbus-libs-1.2.16-8.fc12.i686 expat-2.0.1-7.i686 fontconfig-2.7.3-1.fc12.i686 freetype-2.3.9-6.fc12.i686 gamin-0.1.10-5.fc12.i686 glib2-2.22.2-3.fc12.i686 gtk2-2.18.3-22.fc12.i686 gtk2-engines-2.18.4-4.fc12.i686 gtk2-immodule-xim-2.18.3-22.fc12.i686 gvfs-1.4.2-1.fc12.i686 ibus-gtk-1.2.0.20091124-1.fc12.i686 ibus-libs-1.2.0.20091124-1.fc12.i686 libICE-1.0.6-1.fc12.i686 libSM-1.1.0-7.fc12.i686 libX11-1.3-1.fc12.i686 libXau-1.0.5-1.fc12.i686 libXcomposite-0.4.1-2.fc12.i686 libXcursor-1.1.10-1.fc12.i686 libXdamage-1.1.2-1.fc12.i686 libXext-1.1-1.fc12.i686 libXfixes-4.0.4-1.fc12.i686 libXi-1.3-1.fc12.i686 libXinerama-1.1-1.fc12.i686 libXrandr-1.3.0-3.fc12.i686 libXrender-0.9.5-1.fc12.i686 libXxf86vm-1.1.0-1.fc12.i686 libcanberra-0.22-1.fc12.i686 libcanberra-gtk2-0.22-1.fc12.i686 libcap-ng-0.6.2-3.fc12.i686 libdrm-2.4.15-4.fc12.i686 libjpeg-6b-46.fc12.i686 libogg-1.1.4-2.fc12.i686 libpng-1.2.39-1.fc12.i686 libselinux-2.0.87-1.fc12.i686 libtiff-3.8.2-15.fc12.i686 libtool-ltdl-2.2.6-15.fc12.i686 libudev-145-14.fc12.i686 libuuid-2.16-10.3.fc12.i686 libvorbis-1.2.3-3.fc12.i686 libxcb-1.4-1.fc12.i686 pango-1.26.0-1.fc12.i686 pixman-0.16.2-1.fc12.i686 zlib-1.2.3-23.fc12.i686 (gdb) call glXGetCurrentContext() $1 = (struct __GLXcontextRec *) 0x82546e8 (gdb) It clearly shows a non NULL pointer to the current context. Then there is one remaining question - why the pointer to glGenBuffers is NULL then? Provided that the function is supposed to be existing in the driver? ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
