GEM-dev February 2011

gem-dev@lists.iem.at

10 participants
42 discussions

updated: glsl
by IOhannes m zmoelnig 14 Feb '11

14 Feb '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 i thought it might be a good idea to inform you: glsl_ objects now stopped emitting the shader-IDs for each and every frame. instead, the shaderID is emitted only once, when the shaders are loaded. thus you won't need the [change] object anymore, to prevent [glsl_program] to link a new program for each frame. caveat: currently only valid shaders are sent; if linking fails, you don't know (should be (if needed): 0) fgamsdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1Y9JIACgkQkX2Xpv6ydvR5qwCdGswUxLOAoXpBokLqDQbZmDAO A3kAoLMjtN8KoHbQ+AuCTwQp+cm1XlYQ =0OXa -----END PGP SIGNATURE-----

4 4

update: frei0r
by IOhannes m zmoelnig 14 Feb '11

14 Feb '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 i thought it might be a good idea to inform you: Gem now comes with a simple frei0r wrapper, that allows you to use frei0r source and effect plugins (though not mixer plugins, atm), just like FreeFrame effects. syntax: [pix_frei0r <pluginname>] alternatively: [pix_<pluginname>] fmnasdrt IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1Y8+oACgkQkX2Xpv6ydvR13wCfUKVk7GfP+OwKm1VVqU95HN91 fEMAn0DiBJUTDcokZOnwOPfEeVz5Rxj3 =QymF -----END PGP SIGNATURE-----

1 0

[ pd-gem-Bugs-3177453 ] pix_video with no image crash pix_data
by SourceForge.net 11 Feb '11

11 Feb '11

Bugs item #3177453, was opened at 2011-02-10 16:15 Message generated for change (Settings changed) made by nusmuk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3177453&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pixes (pix_ objects) Group: None >Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Cyrille Henry (nusmuk) Assigned to: Nobody/Anonymous (nobody) Summary: pix_video with no image crash pix_data Initial Comment: using curent svn, ubuntu 10.04 computer with no camera, sending gemhead / pix_video to pix_data crash pd as soon as the gemWin is created. (gdb) backtrace #0 GemPixDualObj::rightRender (this=0x8190570, statePtr=0xbfffe7f8) at GemPixDualObj.cpp:209 #1 0x00565520 in GemPixDualObj::gem_rightMessCallback (data=0x8190080, s=0x8170688, argc=2, argv=0xbfffe550) at GemPixDualObj.cpp:226 #2 0x080ae4d1 in pd_typedmess (x=0x8190080, s=0x8170688, argc=2, argv=0xbfffe550) at m_class.c:681 #3 0x080ae27c in pd_typedmess (x=0x8190640, s=0x814de90, argc=2, argv=0xbfffe550) at m_class.c:765 #4 0x080b0d0f in outlet_anything (x=0x8199840, s=0x814de90, argc=2, argv=0xbfffe550) at m_obj.c:390 #5 0x0053d8a0 in GemBase::continueRender (this=0x8199928, state=0xbfffe7f8) at GemBase.cpp:166 #6 0x0053d96d in GemBase::gem_renderMess (this=0x8199928, cache=0x8199320, state=0xbfffe7f8) at GemBase.cpp:154 #7 0x0053dbd7 in GemBase::gem_MessCallback (data=0x8199370, s=0x814de90, argc=2, argv=0x3903c0) at GemBase.cpp:227 #8 0x080ae4d1 in pd_typedmess (x=0x8199370, s=0x814de90, argc=2, argv=0xbfffe6d8) at m_class.c:681 #9 0x080b0d0f in outlet_anything (x=0x8199338, s=0x814de90, argc=2, argv=0xbfffe6d8) at m_obj.c:390 #10 0x0059e54a in gemhead::renderGL (this=0x81992e8, state=0xbfffe7f8) at gemhead.cpp:110 #11 0x005609ec in GemMan::renderChain (head=0x8199310, state=0xbfffe7f8) ---Type <return> to continue, or q <return> to quit--- at GemMan.cpp:579 #12 0x00561b49 in GemMan::render () at GemMan.cpp:861 #13 0x00562d76 in GemMan::startRendering () at GemMan.cpp:944 #14 0x005a3ead in gemwin::intMess (this=0x819af10, state=1) at gemwin.cpp:102 #15 0x005a3efa in gemwin::floatMessCallback (data=0x819aee8, state=1) at gemwin.cpp:684 #16 0x080b1037 in outlet_float (x=0x819b588, f=1) at m_obj.c:357 #17 0x080b3c88 in binbuf_eval (x=0x819b5a0, target=0x819b574, argc=0, argv=0xbfffed10) at m_binbuf.c:725 #18 0x080b0e7f in outlet_list (x=0x819b3a8, s=0x0, argc=0, argv=0xbfffed10) at m_obj.c:379 #19 0x080ae27c in pd_typedmess (x=0x819b368, s=0x81799b8, argc=0, argv=0xbfffed10) at m_class.c:765 #20 0x080b0d0f in outlet_anything (x=0x819b328, s=0x81799b8, argc=0, argv=0xbfffed10) at m_obj.c:390 #21 0x080ae27c in pd_typedmess (x=0x819b2a0, s=0x81799b8, argc=0, argv=0xbfffed10) at m_class.c:765 #22 0x080ae27c in pd_typedmess (x=0x819b308, s=0x81799b8, argc=0, argv=0xbfffed10) at m_class.c:765 #23 0x080b0d0f in outlet_anything (x=0x819b6c0, s=0x81799b8, argc=0, argv=0xbfffed10) at m_obj.c:390 #24 0x080ae27c in pd_typedmess (x=0x819b6ac, s=0x81799b8, argc=0, argv=0xbfffed10) at m_class.c:765 ---Type <return> to continue, or q <return> to quit--- #25 0x080b3a68 in binbuf_eval (x=0x819b6d8, target=0x819b6ac, argc=1, argv=0xbfffed68) at m_binbuf.c:722 #26 0x08063f7b in message_float (x=0x819b690, xpos=372, ypos=324, shift=0, ctrl=0, alt=0) at g_text.c:349 #27 message_click (x=0x819b690, xpos=372, ypos=324, shift=0, ctrl=0, alt=0) at g_text.c:424 #28 0x080654e0 in text_click (z=0x819b690, glist=0x818f320, xpix=372, ypix=324, shift=0, alt=0, dbl=0, doit=1) at g_text.c:1109 #29 0x0808d21b in gobj_click (x=0x818f320, xpos=372, ypos=324, which=1, mod=<value optimized out>, doit=1) at g_editor.c:108 #30 canvas_doclick (x=0x818f320, xpos=372, ypos=324, which=1, mod=<value optimized out>, doit=1) at g_editor.c:1270 #31 0x0808d9b7 in canvas_mousedown (x=0x818f320, xpos=372, ypos=324, which=1, mod=2) at g_editor.c:1427 #32 0x080ae645 in pd_typedmess (x=0x818f320, s=0x8136e20, argc=4, argv=0xbffff0a0) at m_class.c:744 #33 0x080ae27c in pd_typedmess (x=0x818f2e8, s=0x8136e20, argc=4, argv=0xbffff0a0) at m_class.c:765 #34 0x080b3a68 in binbuf_eval (x=0x8143388, target=0x0, argc=0, argv=0x0) at m_binbuf.c:722 #35 0x080c192f in socketreceiver_read (x=0x8143238, fd=6) at s_inter.c:546 #36 0x080c12ea in sys_domicrosleep (microsec=<value optimized out>, pollem=<value optimized out>) at s_inter.c:184 ---Type <return> to continue, or q <return> to quit--- #37 0x080c1dd2 in sys_pollgui () at s_inter.c:833 #38 0x080bce91 in m_pollingscheduler () at m_sched.c:488 #39 m_mainloop () at m_sched.c:558 #40 0x080c0555 in sys_main (argc=2, argv=0xbffff4e4) at s_main.c:313 #41 0x080c8cbb in main (argc=2, argv=0xbffff4e4) at s_entry.c:32 ---------------------------------------------------------------------- Comment By: IOhannes m zmölnig (zmoelnig) Date: 2011-02-10 16:53 Message: thanks. should be fixed with rev3701 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3177453&group_…

1 0

[ pd-gem-Bugs-3177434 ] deleting a pix_video crash pd
by SourceForge.net 11 Feb '11

11 Feb '11

Bugs item #3177434, was opened at 2011-02-10 15:42 Message generated for change (Settings changed) made by nusmuk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3177434&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Cyrille Henry (nusmuk) Assigned to: Nobody/Anonymous (nobody) Summary: deleting a pix_video crash pd Initial Comment: using curent svn, if i open pix_video help file with a computer that have no camera, removing pix_video object crash pd. no need to open gemWindows. ---------------------------------------------------------------------- Comment By: Cyrille Henry (nusmuk) Date: 2011-02-10 16:11 Message: i realize the crash occur only after having plugged/unplugged the FW device. when removing it, the /dev/raw1394 is still on the file system. the backtrace : (gdb) run Starting program: /usr/local/bin/pd pd/Gem/help/pix_video-help.pd [Thread debugging using libthread_db enabled] open: /etc/pd/gem.conf: No such file or directory open: /home/nusmuk/.pd/gem.conf: No such file or directory open: ./gem.conf: No such file or directory load plugins 'video' in '' pattern : /usr/local/lib/pd/extra/Gem/gem_video*.so dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoDC1394.so'! dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoDS.so'! dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoDV4L.so'! dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoDarwin.so'! dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoHALCON.so'! dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoSGI.so'! dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoUNICAP.so'! dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoV4L.so'! dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoV4L2.so'! dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoVFW.so'! /dev/video0: No such file or directory [New Thread 0xb7619b70 (LWP 2130)] invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb7619b70 (LWP 2130)] gem::video::PIMPL::threadfun (you=0x81a8d50) at video.cpp:189 189 me->m_pimpl->freeze(); (gdb) backtrace #0 gem::video::PIMPL::threadfun (you=0x81a8d50) at video.cpp:189 #1 0x0022596e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x00306a4e in clone () from /lib/tls/i686/cmov/libc.so.6 ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2011-02-10 15:48 Message: you may also use -lib segfault , by matju. it prints a backtrace in the terminal without the need for gdb, and it demangles the C++ symbols as well. it's been posted on pd-list. ---------------------------------------------------------------------- Comment By: IOhannes m zmölnig (zmoelnig) Date: 2011-02-10 15:44 Message: could you provide a backtrace of the crash? on linux/osx/similar you can use gdb for producing one: $ gdb -args /path/to/pd -lib Gem -open /my/faulty/patch.pd [...] (gdb) run [... do something to trigger the crasher bug ...] (gdb) backtrace [...] ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3177434&group_…

1 0

[ pd-gem-Bugs-3177253 ] pix_crop does not work anymore
by SourceForge.net 11 Feb '11

11 Feb '11

Bugs item #3177253, was opened at 2011-02-10 12:13 Message generated for change (Settings changed) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3177253&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pixes (pix_ objects) Group: None >Status: Pending Resolution: Fixed Priority: 7 Private: No Submitted By: Cyrille Henry (nusmuk) Assigned to: Nobody/Anonymous (nobody) Summary: pix_crop does not work anymore Initial Comment: using pix_crop help patch, it did not crop anything. tested with Gem build from 7 feb 2011 it work great on an other computer with Gem from 24 Dec 2010. both computer using ubuntu 10.04 ---------------------------------------------------------------------- Comment By: Cyrille Henry (nusmuk) Date: 2011-02-11 11:57 Message: thanks for the very fast fix. ---------------------------------------------------------------------- Comment By: IOhannes m zmölnig (zmoelnig) Date: 2011-02-10 13:57 Message: fixed in rev3700. thanks for the report. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3177253&group_…

1 0

[ pd-gem-Bugs-3177361 ] no images with FW camera
by SourceForge.net 11 Feb '11

11 Feb '11

Bugs item #3177361, was opened at 2011-02-10 14:02 Message generated for change (Comment added) made by nusmuk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3177361&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pixes (pix_ objects) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Cyrille Henry (nusmuk) Assigned to: Nobody/Anonymous (nobody) Summary: no images with FW camera Initial Comment: hello, with Gem svn, ubuntu 10.04 (kernell 2.6.32), and a guppy pro (from AVT) connected with FW800, i can't have images. (same result with a stingray from AVT) the camera create a device /dev/raw1394 and /dev/video1394/0 i've got video plugin dv4l and dc1394. coriender can grab images without any problem. i don't know if it's related, but when creating pix_video object, i've got an error in the terminal : libdc1394 error: Error: Failed to allocate iso bandwidth libdc1394 error: Error: Failed to setup DMA capture ---------------------------------------------------------------------- >Comment By: Cyrille Henry (nusmuk) Date: 2011-02-11 10:56 Message: if i change line 269 of file videoDC1394.cpp from dc1394speed_t speed=DC1394_ISO_SPEED_400; to dc1394speed_t speed=DC1394_ISO_SPEED_800; iv've got more information about why this speed can't be allocated in the terminal : libdc1394 error: An ISO speed >400Mbps was requested while the camera is in LEGACY mode. Please set the operation mode to OPERATION_MODE_1394B before asking for 1394b ISO speeds libdc1394 error: Error: Failed to allocate iso bandwidth libdc1394 error: Error: Failed to setup DMA capture i just don't know how to do that. any help is apreciated in order to make this work for this camera. ---------------------------------------------------------------------- Comment By: Cyrille Henry (nusmuk) Date: 2011-02-10 15:08 Message: well, i did not have other cam connected when i tried this, so pix_video tried all backend at the initialization. so, i now have a v4l device on the computer. when creating pix_video : no messages regarding 1394. (only a message that say pix_video open a v4l2 device). sending driver dc1394 gives in the terminal : libdc1394 error: Error: Failed to allocate iso bandwidth libdc1394 error: Error: Failed to setup DMA capture and in pd log : error videoDC1394: Generic failure: failed to enumerate then, sending device /dev/raw1394 did not change anything. if i do the other order : recreate pix_video, sending device /dev/raw1394, i've got an error that say V4L can not open this device. then sending driver dc1394 print nothing. the camera is in FW800, the computer have only a FW800 port... ---------------------------------------------------------------------- Comment By: IOhannes m zmölnig (zmoelnig) Date: 2011-02-10 14:15 Message: this happens as soon as you create the [pix_video] object? Gem tries to set the bandwidth to 400 when it _open_s the device, but should fall back to whatever the device gives, if FW400 is not supported. but if the problem already occurs when creating [pix_video] (that is: when initializing the dc1394 infrastructure), it will never reach that... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3177361&group_…

1 0

[ pd-gem-Bugs-3177453 ] pix_video with no image crash pix_data
by SourceForge.net 10 Feb '11

10 Feb '11

Bugs item #3177453, was opened at 2011-02-10 17:15 Message generated for change (Comment added) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3177453&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pixes (pix_ objects) Group: None >Status: Pending >Resolution: Fixed Priority: 5 Private: No Submitted By: Cyrille Henry (nusmuk) Assigned to: Nobody/Anonymous (nobody) Summary: pix_video with no image crash pix_data Initial Comment: using curent svn, ubuntu 10.04 computer with no camera, sending gemhead / pix_video to pix_data crash pd as soon as the gemWin is created. (gdb) backtrace #0 GemPixDualObj::rightRender (this=0x8190570, statePtr=0xbfffe7f8) at GemPixDualObj.cpp:209 #1 0x00565520 in GemPixDualObj::gem_rightMessCallback (data=0x8190080, s=0x8170688, argc=2, argv=0xbfffe550) at GemPixDualObj.cpp:226 #2 0x080ae4d1 in pd_typedmess (x=0x8190080, s=0x8170688, argc=2, argv=0xbfffe550) at m_class.c:681 #3 0x080ae27c in pd_typedmess (x=0x8190640, s=0x814de90, argc=2, argv=0xbfffe550) at m_class.c:765 #4 0x080b0d0f in outlet_anything (x=0x8199840, s=0x814de90, argc=2, argv=0xbfffe550) at m_obj.c:390 #5 0x0053d8a0 in GemBase::continueRender (this=0x8199928, state=0xbfffe7f8) at GemBase.cpp:166 #6 0x0053d96d in GemBase::gem_renderMess (this=0x8199928, cache=0x8199320, state=0xbfffe7f8) at GemBase.cpp:154 #7 0x0053dbd7 in GemBase::gem_MessCallback (data=0x8199370, s=0x814de90, argc=2, argv=0x3903c0) at GemBase.cpp:227 #8 0x080ae4d1 in pd_typedmess (x=0x8199370, s=0x814de90, argc=2, argv=0xbfffe6d8) at m_class.c:681 #9 0x080b0d0f in outlet_anything (x=0x8199338, s=0x814de90, argc=2, argv=0xbfffe6d8) at m_obj.c:390 #10 0x0059e54a in gemhead::renderGL (this=0x81992e8, state=0xbfffe7f8) at gemhead.cpp:110 #11 0x005609ec in GemMan::renderChain (head=0x8199310, state=0xbfffe7f8) ---Type <return> to continue, or q <return> to quit--- at GemMan.cpp:579 #12 0x00561b49 in GemMan::render () at GemMan.cpp:861 #13 0x00562d76 in GemMan::startRendering () at GemMan.cpp:944 #14 0x005a3ead in gemwin::intMess (this=0x819af10, state=1) at gemwin.cpp:102 #15 0x005a3efa in gemwin::floatMessCallback (data=0x819aee8, state=1) at gemwin.cpp:684 #16 0x080b1037 in outlet_float (x=0x819b588, f=1) at m_obj.c:357 #17 0x080b3c88 in binbuf_eval (x=0x819b5a0, target=0x819b574, argc=0, argv=0xbfffed10) at m_binbuf.c:725 #18 0x080b0e7f in outlet_list (x=0x819b3a8, s=0x0, argc=0, argv=0xbfffed10) at m_obj.c:379 #19 0x080ae27c in pd_typedmess (x=0x819b368, s=0x81799b8, argc=0, argv=0xbfffed10) at m_class.c:765 #20 0x080b0d0f in outlet_anything (x=0x819b328, s=0x81799b8, argc=0, argv=0xbfffed10) at m_obj.c:390 #21 0x080ae27c in pd_typedmess (x=0x819b2a0, s=0x81799b8, argc=0, argv=0xbfffed10) at m_class.c:765 #22 0x080ae27c in pd_typedmess (x=0x819b308, s=0x81799b8, argc=0, argv=0xbfffed10) at m_class.c:765 #23 0x080b0d0f in outlet_anything (x=0x819b6c0, s=0x81799b8, argc=0, argv=0xbfffed10) at m_obj.c:390 #24 0x080ae27c in pd_typedmess (x=0x819b6ac, s=0x81799b8, argc=0, argv=0xbfffed10) at m_class.c:765 ---Type <return> to continue, or q <return> to quit--- #25 0x080b3a68 in binbuf_eval (x=0x819b6d8, target=0x819b6ac, argc=1, argv=0xbfffed68) at m_binbuf.c:722 #26 0x08063f7b in message_float (x=0x819b690, xpos=372, ypos=324, shift=0, ctrl=0, alt=0) at g_text.c:349 #27 message_click (x=0x819b690, xpos=372, ypos=324, shift=0, ctrl=0, alt=0) at g_text.c:424 #28 0x080654e0 in text_click (z=0x819b690, glist=0x818f320, xpix=372, ypix=324, shift=0, alt=0, dbl=0, doit=1) at g_text.c:1109 #29 0x0808d21b in gobj_click (x=0x818f320, xpos=372, ypos=324, which=1, mod=<value optimized out>, doit=1) at g_editor.c:108 #30 canvas_doclick (x=0x818f320, xpos=372, ypos=324, which=1, mod=<value optimized out>, doit=1) at g_editor.c:1270 #31 0x0808d9b7 in canvas_mousedown (x=0x818f320, xpos=372, ypos=324, which=1, mod=2) at g_editor.c:1427 #32 0x080ae645 in pd_typedmess (x=0x818f320, s=0x8136e20, argc=4, argv=0xbffff0a0) at m_class.c:744 #33 0x080ae27c in pd_typedmess (x=0x818f2e8, s=0x8136e20, argc=4, argv=0xbffff0a0) at m_class.c:765 #34 0x080b3a68 in binbuf_eval (x=0x8143388, target=0x0, argc=0, argv=0x0) at m_binbuf.c:722 #35 0x080c192f in socketreceiver_read (x=0x8143238, fd=6) at s_inter.c:546 #36 0x080c12ea in sys_domicrosleep (microsec=<value optimized out>, pollem=<value optimized out>) at s_inter.c:184 ---Type <return> to continue, or q <return> to quit--- #37 0x080c1dd2 in sys_pollgui () at s_inter.c:833 #38 0x080bce91 in m_pollingscheduler () at m_sched.c:488 #39 m_mainloop () at m_sched.c:558 #40 0x080c0555 in sys_main (argc=2, argv=0xbffff4e4) at s_main.c:313 #41 0x080c8cbb in main (argc=2, argv=0xbffff4e4) at s_entry.c:32 ---------------------------------------------------------------------- >Comment By: IOhannes m zmölnig (zmoelnig) Date: 2011-02-10 17:53 Message: thanks. should be fixed with rev3701 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3177453&group_…

1 0

[ pd-gem-Bugs-3177453 ] pix_video with no image crash pix_data
by SourceForge.net 10 Feb '11

10 Feb '11

Bugs item #3177453, was opened at 2011-02-10 16:15 Message generated for change (Tracker Item Submitted) made by nusmuk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3177453&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pixes (pix_ objects) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Cyrille Henry (nusmuk) Assigned to: Nobody/Anonymous (nobody) Summary: pix_video with no image crash pix_data Initial Comment: using curent svn, ubuntu 10.04 computer with no camera, sending gemhead / pix_video to pix_data crash pd as soon as the gemWin is created. (gdb) backtrace #0 GemPixDualObj::rightRender (this=0x8190570, statePtr=0xbfffe7f8) at GemPixDualObj.cpp:209 #1 0x00565520 in GemPixDualObj::gem_rightMessCallback (data=0x8190080, s=0x8170688, argc=2, argv=0xbfffe550) at GemPixDualObj.cpp:226 #2 0x080ae4d1 in pd_typedmess (x=0x8190080, s=0x8170688, argc=2, argv=0xbfffe550) at m_class.c:681 #3 0x080ae27c in pd_typedmess (x=0x8190640, s=0x814de90, argc=2, argv=0xbfffe550) at m_class.c:765 #4 0x080b0d0f in outlet_anything (x=0x8199840, s=0x814de90, argc=2, argv=0xbfffe550) at m_obj.c:390 #5 0x0053d8a0 in GemBase::continueRender (this=0x8199928, state=0xbfffe7f8) at GemBase.cpp:166 #6 0x0053d96d in GemBase::gem_renderMess (this=0x8199928, cache=0x8199320, state=0xbfffe7f8) at GemBase.cpp:154 #7 0x0053dbd7 in GemBase::gem_MessCallback (data=0x8199370, s=0x814de90, argc=2, argv=0x3903c0) at GemBase.cpp:227 #8 0x080ae4d1 in pd_typedmess (x=0x8199370, s=0x814de90, argc=2, argv=0xbfffe6d8) at m_class.c:681 #9 0x080b0d0f in outlet_anything (x=0x8199338, s=0x814de90, argc=2, argv=0xbfffe6d8) at m_obj.c:390 #10 0x0059e54a in gemhead::renderGL (this=0x81992e8, state=0xbfffe7f8) at gemhead.cpp:110 #11 0x005609ec in GemMan::renderChain (head=0x8199310, state=0xbfffe7f8) ---Type <return> to continue, or q <return> to quit--- at GemMan.cpp:579 #12 0x00561b49 in GemMan::render () at GemMan.cpp:861 #13 0x00562d76 in GemMan::startRendering () at GemMan.cpp:944 #14 0x005a3ead in gemwin::intMess (this=0x819af10, state=1) at gemwin.cpp:102 #15 0x005a3efa in gemwin::floatMessCallback (data=0x819aee8, state=1) at gemwin.cpp:684 #16 0x080b1037 in outlet_float (x=0x819b588, f=1) at m_obj.c:357 #17 0x080b3c88 in binbuf_eval (x=0x819b5a0, target=0x819b574, argc=0, argv=0xbfffed10) at m_binbuf.c:725 #18 0x080b0e7f in outlet_list (x=0x819b3a8, s=0x0, argc=0, argv=0xbfffed10) at m_obj.c:379 #19 0x080ae27c in pd_typedmess (x=0x819b368, s=0x81799b8, argc=0, argv=0xbfffed10) at m_class.c:765 #20 0x080b0d0f in outlet_anything (x=0x819b328, s=0x81799b8, argc=0, argv=0xbfffed10) at m_obj.c:390 #21 0x080ae27c in pd_typedmess (x=0x819b2a0, s=0x81799b8, argc=0, argv=0xbfffed10) at m_class.c:765 #22 0x080ae27c in pd_typedmess (x=0x819b308, s=0x81799b8, argc=0, argv=0xbfffed10) at m_class.c:765 #23 0x080b0d0f in outlet_anything (x=0x819b6c0, s=0x81799b8, argc=0, argv=0xbfffed10) at m_obj.c:390 #24 0x080ae27c in pd_typedmess (x=0x819b6ac, s=0x81799b8, argc=0, argv=0xbfffed10) at m_class.c:765 ---Type <return> to continue, or q <return> to quit--- #25 0x080b3a68 in binbuf_eval (x=0x819b6d8, target=0x819b6ac, argc=1, argv=0xbfffed68) at m_binbuf.c:722 #26 0x08063f7b in message_float (x=0x819b690, xpos=372, ypos=324, shift=0, ctrl=0, alt=0) at g_text.c:349 #27 message_click (x=0x819b690, xpos=372, ypos=324, shift=0, ctrl=0, alt=0) at g_text.c:424 #28 0x080654e0 in text_click (z=0x819b690, glist=0x818f320, xpix=372, ypix=324, shift=0, alt=0, dbl=0, doit=1) at g_text.c:1109 #29 0x0808d21b in gobj_click (x=0x818f320, xpos=372, ypos=324, which=1, mod=<value optimized out>, doit=1) at g_editor.c:108 #30 canvas_doclick (x=0x818f320, xpos=372, ypos=324, which=1, mod=<value optimized out>, doit=1) at g_editor.c:1270 #31 0x0808d9b7 in canvas_mousedown (x=0x818f320, xpos=372, ypos=324, which=1, mod=2) at g_editor.c:1427 #32 0x080ae645 in pd_typedmess (x=0x818f320, s=0x8136e20, argc=4, argv=0xbffff0a0) at m_class.c:744 #33 0x080ae27c in pd_typedmess (x=0x818f2e8, s=0x8136e20, argc=4, argv=0xbffff0a0) at m_class.c:765 #34 0x080b3a68 in binbuf_eval (x=0x8143388, target=0x0, argc=0, argv=0x0) at m_binbuf.c:722 #35 0x080c192f in socketreceiver_read (x=0x8143238, fd=6) at s_inter.c:546 #36 0x080c12ea in sys_domicrosleep (microsec=<value optimized out>, pollem=<value optimized out>) at s_inter.c:184 ---Type <return> to continue, or q <return> to quit--- #37 0x080c1dd2 in sys_pollgui () at s_inter.c:833 #38 0x080bce91 in m_pollingscheduler () at m_sched.c:488 #39 m_mainloop () at m_sched.c:558 #40 0x080c0555 in sys_main (argc=2, argv=0xbffff4e4) at s_main.c:313 #41 0x080c8cbb in main (argc=2, argv=0xbffff4e4) at s_entry.c:32 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3177453&group_…

1 0

[ pd-gem-Bugs-3177434 ] deleting a pix_video crash pd
by SourceForge.net 10 Feb '11

10 Feb '11

Bugs item #3177434, was opened at 2011-02-10 15:42 Message generated for change (Comment added) made by nusmuk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3177434&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Cyrille Henry (nusmuk) Assigned to: Nobody/Anonymous (nobody) Summary: deleting a pix_video crash pd Initial Comment: using curent svn, if i open pix_video help file with a computer that have no camera, removing pix_video object crash pd. no need to open gemWindows. ---------------------------------------------------------------------- >Comment By: Cyrille Henry (nusmuk) Date: 2011-02-10 16:11 Message: i realize the crash occur only after having plugged/unplugged the FW device. when removing it, the /dev/raw1394 is still on the file system. the backtrace : (gdb) run Starting program: /usr/local/bin/pd pd/Gem/help/pix_video-help.pd [Thread debugging using libthread_db enabled] open: /etc/pd/gem.conf: No such file or directory open: /home/nusmuk/.pd/gem.conf: No such file or directory open: ./gem.conf: No such file or directory load plugins 'video' in '' pattern : /usr/local/lib/pd/extra/Gem/gem_video*.so dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoDC1394.so'! dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoDS.so'! dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoDV4L.so'! dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoDarwin.so'! dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoHALCON.so'! dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoSGI.so'! dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoUNICAP.so'! dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoV4L.so'! dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoV4L2.so'! dylib loading file '/usr/local/lib/pd/extra/Gem/gem_videoVFW.so'! /dev/video0: No such file or directory [New Thread 0xb7619b70 (LWP 2130)] invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" invalid command name ".x81b2670.c" Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb7619b70 (LWP 2130)] gem::video::PIMPL::threadfun (you=0x81a8d50) at video.cpp:189 189 me->m_pimpl->freeze(); (gdb) backtrace #0 gem::video::PIMPL::threadfun (you=0x81a8d50) at video.cpp:189 #1 0x0022596e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x00306a4e in clone () from /lib/tls/i686/cmov/libc.so.6 ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2011-02-10 15:48 Message: you may also use -lib segfault , by matju. it prints a backtrace in the terminal without the need for gdb, and it demangles the C++ symbols as well. it's been posted on pd-list. ---------------------------------------------------------------------- Comment By: IOhannes m zmölnig (zmoelnig) Date: 2011-02-10 15:44 Message: could you provide a backtrace of the crash? on linux/osx/similar you can use gdb for producing one: $ gdb -args /path/to/pd -lib Gem -open /my/faulty/patch.pd [...] (gdb) run [... do something to trigger the crasher bug ...] (gdb) backtrace [...] ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3177434&group_…

1 0

[ pd-gem-Bugs-3177434 ] deleting a pix_video crash pd
by SourceForge.net 10 Feb '11

10 Feb '11

Bugs item #3177434, was opened at 2011-02-10 16:42 Message generated for change (Comment added) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3177434&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Cyrille Henry (nusmuk) Assigned to: Nobody/Anonymous (nobody) Summary: deleting a pix_video crash pd Initial Comment: using curent svn, if i open pix_video help file with a computer that have no camera, removing pix_video object crash pd. no need to open gemWindows. ---------------------------------------------------------------------- Comment By: IOhannes m zmölnig (zmoelnig) Date: 2011-02-10 16:44 Message: could you provide a backtrace of the crash? on linux/osx/similar you can use gdb for producing one: $ gdb -args /path/to/pd -lib Gem -open /my/faulty/patch.pd [...] (gdb) run [... do something to trigger the crasher bug ...] (gdb) backtrace [...] ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3177434&group_…

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

GEM-dev February 2011