明覺 wrote: > 2009/5/12 明覺 <[email protected]>: >> 2009/5/12 Ian Romanick <[email protected]>: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> 明覺 wrote: >>>> Greetings! >>>> my application crashes at line 660 of glxcmds.c, here is the gdb info: >>>> --------------------------------------------------------------------------------------- >>>> (gdb) break glxcmds.c:660 >>>> Breakpoint 1 (glxcmds.c:660) pending. >>>> (gdb) run >>>> Breakpoint 1, glXWaitX () at glxcmds.c:660 >>>> (gdb) print psc->driScreen->waitX >>>> $3 = (void (*)(__GLXDRIdrawable *)) 0x47206769666e6f63 >>>> (gdb) print *psc->driScreen->waitX >>>> Cannot access memory at address 0x47206769666e6f63 >>>> (gdb) step >>>> Program received signal SIGSEGV, Segmentation fault. >>>> --------------------------------------------------------------------------------------- >>>> is it a bug of mesa or something wrong in my application? thanks >>> It's a known bug in Mesa. I believe that this is already fixed, so you >>> should just need to update Mesa. >> I'm using mesa 7.4.1, is the bug fixed in 7.5? I will try it. thanks > > I installed http://www.mesa3d.org/beta/MesaLib-7.6-devel-20090501.tar.gz > into /usr to overwrite the old mesa-7.4.1, and exed ldconfig, then > rebuilt my program by kdevelop, the previous "seg fault" error > disappear, but another new one appear, seems to be associated with the > glLightfv function, any advice to solve the new one? here is the gdb > info: > ------------------------------------------------------------------------------------------------------------------------------ > minjue:~/workspace/k3dsurf/k3dsurf-0.6.2/bin# gdb k3dsurf > GNU gdb (GDB) 6.8.50.20090106-cvs-debian > This GDB was configured as "x86_64-linux-gnu". > (gdb) break glviewer.cpp:740 > Breakpoint 1 at 0x472920: file glviewer.cpp, line 740. (2 locations) > (gdb) run > Starting program: /root/workspace/k3dsurf/k3dsurf-0.6.2/bin/k3dsurf > [Thread debugging using libthread_db enabled] > > Breakpoint 1, OpenGlWidget (this=0xa34a10, parent=<value optimized out>, > name=<value optimized out>) at glviewer.cpp:740 > 740 glLightfv(GL_LIGHT0, GL_AMBIENT, ambient); > (gdb) print GL_LIGHT0 > No symbol "GL_LIGHT0" in current context. > (gdb) print GL_AMBIENT > No symbol "GL_AMBIENT" in current context. > (gdb) print ambient > $1 = {0, 0, -4.28388841e+32, 4.59163468e-41} > (gdb) step > 736 GLfloat lmodel_ambient[] = { 0.2, 0.2, 0.2, 1.0 }; > (gdb) > 740 glLightfv(GL_LIGHT0, GL_AMBIENT, ambient); > (gdb) > 734 GLfloat ambient[] = { .0, .0, .0, 1.0 }; > (gdb) > 735 GLfloat diffuse[] = { 1.0, 1.0, 1.0, 1.0 }; > (gdb) > 736 GLfloat lmodel_ambient[] = { 0.2, 0.2, 0.2, 1.0 }; > (gdb) > 737 GLfloat local_view[] = { 1.0 }; > (gdb) > 740 glLightfv(GL_LIGHT0, GL_AMBIENT, ambient); > (gdb) > glLightfv () at ../../../src/mesa/x86-64/glapi_x86-64.S:5622 > 5622 pushq %rdi > Current language: auto; currently asm > (gdb) > glLightfv () at ../../../src/mesa/x86-64/glapi_x86-64.S:5623 > 5623 pushq %rsi > (gdb) > glLightfv () at ../../../src/mesa/x86-64/glapi_x86-64.S:5624 > 5624 pushq %rdx > (gdb) > glLightfv () at ../../../src/mesa/x86-64/glapi_x86-64.S:5625 > 5625 call _x86_64_get_dispa...@plt > (gdb) > _x86_64_get_dispatch () at ../../../src/mesa/x86-64/glapi_x86-64.S:76 > 76 movq _gl_DispatchTSD(%rip), %rdi > (gdb) > 77 jmp pthread_getspeci...@plt > (gdb) > 0x00007ffff6524840 in pthread_getspecific () from /lib/libpthread.so.0 > (gdb) > Single stepping until exit from function pthread_getspecific, > which has no line number information. > glLightfv () at ../../../src/mesa/x86-64/glapi_x86-64.S:5626 > 5626 popq %rdx > (gdb) > glLightfv () at ../../../src/mesa/x86-64/glapi_x86-64.S:5627 > 5627 popq %rsi > (gdb) > glLightfv () at ../../../src/mesa/x86-64/glapi_x86-64.S:5628 > 5628 popq %rdi > (gdb) > glLightfv () at ../../../src/mesa/x86-64/glapi_x86-64.S:5629 > 5629 movq 1280(%rax), %r11 > (gdb) > 5630 jmp *%r11 > (gdb) > > Program received signal SIGSEGV, Segmentation fault. > 0x0000000000000000 in ?? ()
Have you tried valgrind again? -Brian ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
