Alright, well, this isn't going to yield as much information as you'd like, I'm afraid. I have the debugger attached to the process at the moment, and am attaching the debug session. However, when I did "p gst_object_get_name(0x169ee30)" (0x169ee30 being the pad number this time around) after the SIGABRT, I was greeted with:
========== (gdb) p gst_object_get_name(0x169ee30) [Thread 0x43abf950 (LWP 8863) exited] ========== Banshee was responsive again, tried to activate a new song, and that of course failed. I gave a SIGINT, and got: ========== [Thread 0x43abf950 (LWP 9304) exited] ^C Program received signal SIGINT, Interrupt. [Switching to Thread 0x7f99deb98710 (LWP 8581)] 0x00007f99ddeb0b04 in __lll_lock_wait () from /lib/libpthread.so.0 The program being debugged was signaled while in a function called from GDB. GDB remains in the frame where the signal was received. To change this behavior use "set unwindonsignal on" Evaluation of the expression containing the function (gst_object_get_name) will be abandoned. ========== Alright, so I tried to continue a few times, failing of course. So, I did another backtrace and found out that gst_object_get_parent(...) was calling for a mutex, and hanging on attempting to get it. I don't know how to work around that. I'll leave the debugger active for now... Any advice on how to proceed from here? The entire debugging session so far is attached. ** Attachment added: "Debugging session" http://launchpadlibrarian.net/18408136/debug-session.txt -- GStreamer update (7-Oct-2008, Intrepid) causes Banshee crash https://bugs.launchpad.net/bugs/279800 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
