Hello!
I have a small problem running Gem. I tried 0.90 and latest CVS on FC6. Whenever I destroy or close Gem window segfault is issued and pd dies. gdb using latest CVS reveals that they are two different problems. First there is a gdb bt for destroying a window sending destroy to gemwin. The second is bt for closing the Gem window from window manager
I don't really know how to get more debugging info inside Gem.pd_linux and libGL.so.1 (using debuginfo with libGL.so.1 makes pd not to run insode gdb(?)).
Any ideas, what to try next?
Thanks and take care, M.
--------------- (gdb) run Starting program: /usr/local/bin/pd -lib Gem [Thread debugging using libthread_db enabled] [New Thread -1208432960 (LWP 22866)]
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208432960 (LWP 22866)] 0x00f19880 in ?? () (gdb) bt #0 0x00f19880 in ?? () #1 0x02058d3c in glXDestroyContext () from /usr/lib/libGL.so.1 #2 0x0205af1f in glXMakeCurrentReadSGI () from /usr/lib/libGL.so.1 #3 0x0205b1c3 in glXMakeCurrent () from /usr/lib/libGL.so.1 #4 0x001ebca6 in GemMan::destroyWindow () from /usr/local/lib/pd/extra/Gem.pd_linux #5 0x002690b7 in gemwin::destroyMessCallback () from /usr/local/lib/pd/extra/Gem.pd_linux #6 0x080a6a9f in pd_typedmess (x=0x96c1a48, s=0x96b6110, argc=0, argv=0x81193d0) at m_class.c:728 #7 0x080a9ae9 in outlet_anything (x=0x96c1c00, s=0x96b6110, argc=0, argv=0x81193d0) at m_obj.c:387 #8 0x080a6706 in pd_typedmess (x=0x96c1bec, s=0x96b6110, argc=<value optimized out>, argv=0x81193d0) at m_class.c:749 #9 0x080aad8d in binbuf_eval (x=0x96c1b30, target=0x96c1bec, argc=1, argv=0xbfd9d13c) at m_binbuf.c:673 #10 0x0805eadb in message_click (x=0x96c1bd0, xpos=69, ypos=91, shift=0, ctrl=0, alt=0) at g_text.c:300 #11 0x08062d81 in text_click (z=0x96c1bd0, glist=0x96c18e0, xpix=69, ypix=91, shift=0, alt=0, dbl=0, doit=1) at g_text.c:1065 #12 0x0808971c in canvas_doclick (x=0x96c18e0, xpos=69, ypos=91, which=1, mod=0, doit=1) at g_editor.c:92 #13 0x0808a4c7 in canvas_mousedown (x=0x96c18e0, xpos=69, ypos=91, which=1, mod=0) at g_editor.c:1242 #14 0x080a6a9f in pd_typedmess (x=0x96c18e0, s=0x9679c40, argc=4, argv=0x81193a8) at m_class.c:728 #15 0x080a6706 in pd_typedmess (x=0x96c1dc0, s=0x9679c40, argc=<value optimized out>, argv=0x81193a8) at m_class.c:749 #16 0x080aad8d in binbuf_eval (x=0x9686378, target=0x96c1dc0, argc=0, argv=0x0) at m_binbuf.c:673 #17 0x080b881b in socketreceiver_read (x=0x9686398, fd=7) at s_inter.c:540 #18 0x080b5c49 in sys_domicrosleep (microsec=<value optimized out>, pollem=<value optimized out>) at s_inter.c:180 #19 0x080b6c77 in sys_pollgui () at s_inter.c:825 #20 0x080b2317 in m_scheduler () at m_sched.c:466 #21 0x080b580a in sys_main (argc=3, argv=0xbfd9ece4) at s_main.c:316 #22 0x080bea0f in main (argc=Cannot access memory at address 0x0 ) at s_entry.c:27 (gdb) ----------- (gdb) run Starting program: /usr/local/bin/pd -lib Gem [Thread debugging using libthread_db enabled] [New Thread -1209059648 (LWP 31376)]
Program received signal SIGPIPE, Broken pipe. [Switching to Thread -1209059648 (LWP 31376)] 0x004eb402 in __kernel_vsyscall () (gdb) bt #0 0x004eb402 in __kernel_vsyscall () #1 0x00d12cc3 in __write_nocancel () from /lib/libpthread.so.0 #2 0x0721aa9e in _X11TransGetConnectionNumber () from /usr/lib/libX11.so.6 #3 0x0721a7af in _X11TransWrite () from /usr/lib/libX11.so.6 #4 0x072206b7 in _XSend () from /usr/lib/libX11.so.6 #5 0x0722078b in _XReply () from /usr/lib/libX11.so.6 #6 0x0207912f in XF86DRIGetDrawableInfo () from /usr/lib/libGL.so.1 #7 0x010d74af in __driUtilUpdateDrawableInfo () from /usr/lib/dri/r200_dri.so #8 0x010de6d0 in r200GetLock () from /usr/lib/dri/r200_dri.so #9 0x010de466 in r200RefillCurrentDmaRegion () from /usr/lib/dri/r200_dri.so #10 0x01103ddd in VFMT_FALLBACK () from /usr/lib/dri/r200_dri.so #11 0x0097c218 in disk::render () from /usr/local/lib/pd/extra/Gem.pd_linux #12 0x008e64cc in GemBase::gem_renderMess () from /usr/local/lib/pd/extra/Gem.pd_linux #13 0x008e68bb in GemBase::gem_MessCallback () from /usr/local/lib/pd/extra/Gem.pd_linux #14 0x080a680b in pd_typedmess (x=0x865bef0, s=0x861fde0, argc=<value optimized out>, argv=0xbfe06ca0) at m_class.c:665 #15 0x080a9ae9 in outlet_anything (x=0x865bc08, s=0x861fde0, argc=2, argv=0xbfe06ca0) at m_obj.c:387 #16 0x008e6470 in GemBase::continueRender () from /usr/local/lib/pd/extra/Gem.pd_linux #17 0x008e64d8 in GemBase::gem_renderMess () from /usr/local/lib/pd/extra/Gem.pd_linux #18 0x008e68bb in GemBase::gem_MessCallback () from /usr/local/lib/pd/extra/Gem.pd_linux #19 0x080a680b in pd_typedmess (x=0x865bbb0, s=0x861fde0, argc=<value optimized out>, argv=0xbfe06ddc) at m_class.c:665 #20 0x080a9ae9 in outlet_anything (x=0x865ab70, s=0x861fde0, argc=2, argv=0xbfe06ddc) at m_obj.c:387 #21 0x0096fa58 in gemhead::renderGL () from /usr/local/lib/pd/extra/Gem.pd_linux #22 0x008f5dfe in GemMan::renderChain () from /usr/local/lib/pd/extra/Gem.pd_linux #23 0x008f629d in GemMan::render () from /usr/local/lib/pd/extra/Gem.pd_linux #24 0x080b194b in sched_tick (next_sys_time=1093836800) at m_sched.c:355 #25 0x080b266e in m_scheduler () at m_sched.c:460 #26 0x080b580a in sys_main (argc=3, argv=0xbfe07554) at s_main.c:316 #27 0x080bea0f in main (argc=199040, argv=0x0) at s_entry.c:27 (gdb)
Miha Tomšič wrote:
Hello!
I have a small problem running Gem. I tried 0.90 and latest CVS on FC6. Whenever I destroy or close Gem window segfault is issued and pd dies. gdb using latest CVS reveals that they are two different problems. First there is a gdb bt for destroying a window sending destroy to gemwin. The second is bt for closing the Gem window from window manager
I don't really know how to get more debugging info inside Gem.pd_linux and libGL.so.1 (using debuginfo with libGL.so.1 makes pd not to run insode gdb(?)).
Any ideas, what to try next?
which card are you using? (i guess a radeon). have you tried with another card (e.g. nvidia)?
mfga.sdr IOhannes
Hello, IOhannes!
On 11/26/06, IOhannes m zmoelnig zmoelnig@iem.at wrote:
which card are you using? (i guess a radeon).
Yes, Radeon Mobility 9000 which is not supported by latest ATI's proprietary drivers. I have to check the status and availability of older drivers that still supported this chip. Will probably have to do some compiling and packaging for current FC6 kernel. Will be posting what I find out.
have you tried with another card (e.g. nvidia)?
OK, tried it on the other computer with nvidia (and their drivers) and basically the same FC6 setup. There are no problems destroying or closing the window. No segfaults or broken pipes. Nvidia provides their own libGL, right? I'll try different version of libGL on the radeon computer. I can try using older mesa open source drivers/libGL for radeon 6.4.2 - don't know if it supports my chip at all.
And one small correction to the bt's I sent before - those were for 0.90 version of Gem. So here is the 0.91-cvs output. Using correct versions of debuginfo and libraries I got bit more info of where it crashes. I guess it is a libGL problem. I should mention that I have no problem running or closing any other GL apps with the same libGL.
Thanks for now and take care, Miha
---------------- (gdb) run Starting program: /usr/local/bin/pd -lib Gem [Thread debugging using libthread_db enabled] [New Thread -1208682816 (LWP 9600)] Vertex3f: 2 Normal3f: 2
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208682816 (LWP 9600)] 0x017f2880 in ?? () (gdb) bt #0 0x017f2880 in ?? () #1 0x0376dd3c in BindContextWrapper (dpy=0x8cc5a30, gc=0x8d23118, draw=<value optimized out>, read=39845892) at glxext.c:1542 #2 0x0376ff1f in MakeContextCurrent (dpy=0x8cc5a30, draw=39845892, read=39845892, gc=0x8d23118) at glxext.c:1630 #3 0x037701c3 in glXMakeCurrent (dpy=0x8cc5a30, draw=39845892, gc=0x8d23118) at glxext.c:1792 #4 0x00779046 in GemMan::destroyWindow () at GemMan.cpp:1303 #5 0x007797a5 in GemMan::render () at GemMan.cpp:749 #6 0x080b194b in sched_tick (next_sys_time=1511854080) at m_sched.c:355 #7 0x080b266e in m_scheduler () at m_sched.c:460 #8 0x080b580a in sys_main (argc=3, argv=0xbffaef44) at s_main.c:316 #9 0x080bea0f in main (argc=Cannot access memory at address 0x0 ) at s_entry.c:27 (gdb) --------------
Hallo, IOhannes m zmoelnig hat gesagt: // IOhannes m zmoelnig wrote:
which card are you using? (i guess a radeon). have you tried with another card (e.g. nvidia)?
I get the same crash with my Matrox G450 on Debian, latest and greatest testing, Gem-CVS, Pd-CVS-MAIN.
(gdb) bt #0 0xb555ea30 in ?? () #1 0xb783fcec in glXDestroyContext () from /usr/lib/libGL.so.1 #2 0xb7841df0 in glXMakeCurrentReadSGI () from /usr/lib/libGL.so.1 #3 0xb7842083 in glXMakeCurrent () from /usr/lib/libGL.so.1 #4 0xb7b7334f in GemMan::destroyWindow () from /usr/lib/pd/extra/Gem.pd_linux #5 0xb7bd2ea7 in gemwin::destroyMessCallback () from /usr/lib/pd/extra/Gem.pd_linux #6 0x0809fd15 in pd_typedmess (x=0x0, s=0x3c, argc=0, argv=0x810e750) at m_class.c:728 Previous frame inner to this frame (corrupt stack?)
Ciao
Hello, Frank!
On 12/3/06, Frank Barknecht fbar@footils.org wrote:
I get the same crash with my Matrox G450 on Debian, latest and greatest testing, Gem-CVS, Pd-CVS-MAIN.
(gdb) bt #0 0xb555ea30 in ?? () #1 0xb783fcec in glXDestroyContext () from /usr/lib/libGL.so.1 #2 0xb7841df0 in glXMakeCurrentReadSGI () from /usr/lib/libGL.so.1 #3 0xb7842083 in glXMakeCurrent () from /usr/lib/libGL.so.1 #4 0xb7b7334f in GemMan::destroyWindow () from /usr/lib/pd/extra/Gem.pd_linux #5 0xb7bd2ea7 in gemwin::destroyMessCallback () from /usr/lib/pd/extra/Gem.pd_linux #6 0x0809fd15 in pd_typedmess (x=0x0, s=0x3c, argc=0, argv=0x810e750) at m_class.c:728 Previous frame inner to this frame (corrupt stack?)
As much as I found out this is a mesa-libGL issue - you are using it, right? I have this problem with Mesa 6.5.1 and 6.5.2 from CVS. Using older/stable version 6.4.2 works fine for me. I already filed a bug in bugzilla for mesa.
Take care, Miha
-
Frank Barknecht -
Georg Holzmann -
IOhannes m zmoelnig -
Miha Tomšič