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...
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...
-
SourceForge.net