GNOME Bugzilla – Bug 419513
crash in Sound: testing sound
Last modified: 2007-03-18 17:30:06 UTC
Version: 2.16.3 What were you doing when the application crashed? testing sound Distribution: Unknown Gnome Release: 2.16.3 2007-03-14 (FreeBSD GNOME Project) BugBuddy Version: 2.16.1 System: FreeBSD 6.2-RELEASE-p2 FreeBSD 6.2-RELEASE-p2 #0: Thu Mar 15 19:10:16 EET 2007 kh54@FBSD.lan:/usr/obj/usr/src/sys/MYKERNEL6_2 i386 X Vendor: The X.Org Foundation X Vendor Release: 60900000 Selinux: No Accessibility: Disabled Memory status: size: 33052 vsize: 0 resident: 33052 share: 0 rss: 16660 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 256 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/local/bin/gnome-sound-properties' (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 0x83e9800 (sleeping)] [New Thread 0x83e9600 (LWP 100114)] [New Thread 0x8064000 (runnable)] [New LWP 100115] [Switching to LWP 100115] 0x290a84f7 in pthread_testcancel () from /lib/libpthread.so.2
+ Trace 119545
Thread 4 (LWP 100115)
Thread 3 (Thread 0x8064000 (runnable))
----------- .xsession-errors --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 warning: Unable to get location for thread creation breakpoint: generic error ** Message: drive = 0 ** Message: volume = 0 Unhandled dwarf expression opcode 0x93 Unhandled dwarf expression opcode 0x93 /usr/local/share/gnome/bug-buddy/gdb-cmd:2: Error in sourced command file: Previous frame inner to this frame (corrupt stack?) --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 413801 ***