GNOME Bugzilla – Bug 337519
after exiting ekiga , cpu goes to 100% and dump core
Last modified: 2006-12-26 19:46:57 UTC
Please describe the problem: After I exit ekiga , it uses the cpu to the fullist , 100%. lots of text prints to the shell which ran ekiga, it looks like a core dump to the terminal. Then I must Ctrl+c to stop ekiga. Steps to reproduce: 1. load ekiga from the shell 2. quit ekiga 3. Actual results: see description above Expected results: nice clean quit Does this happen every time? yes Other information: Gentoo using 2.6.17-rc1 gcc 3.4.6 I tried a complete uninstall and reinstall. Ekiga 1.99 worked fine here.. odd
Please provide a -d 4 debug output.
how may I capture all the text that is dumpped to the gdb terminal after quitting? should I pipe it to a file? $gdb -d 4 `which ekiga` >>ekiga.log sorry I am new to gdb ?
an easy way is to use script. Type "script" start gdb ekiga run the program make it crash type Ctrl-D the script will be in the directory
I am currently getting this: (gdb) run Starting program: /usr/bin/ekiga [Thread debugging using libthread_db enabled] [New Thread -1242847008 (LWP 28930)] [New Thread -1244267600 (LWP 28936)] [New Thread -1244533840 (LWP 28937)] Block 0x8164998 not in heap! Block 0x8164998 not in heap! Block 0x82be158 not in heap! Block 0x82be158 not in heap! Block 0x816e568 not in heap! Block 0x8164338 not in heap! Block 0x8164338 not in heap! Block 0x8164998 not in heap! Block 0x816e690 not in heap! [New Thread -1257518160 (LWP 28938)] [New Thread -1258587216 (LWP 28944)] [New Thread -1258853456 (LWP 28945)] Block 0x85d9908 not in heap! Block 0x85d9908 not in heap! Block 0x85d9f58 not in heap! Block 0x82c07e8 not in heap! Block 0x85da188 not in heap! Block 0x85da188 not in heap! Block 0x85d68e0 not in heap! Block 0x85d68e0 not in heap! Block 0x82bf6a0 not in heap! [New Thread -1267553360 (LWP 28952)] [New Thread -1270281296 (LWP 28953)] [New Thread -1267819600 (LWP 28954)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1242847008 (LWP 28930)] 0xb66fead3 in pthread_create@@GLIBC_2.1 () from /lib/tls/libpthread.so.0 (gdb) quit it used to run should I rebuild ekiga?
Created attachment 62982 [details] typescript of gdb crashing ekiga hope it helps
You attached an ebuild, not the typescript...
Is the problem still current ?
Created attachment 64098 [details] typescript from gdb after crash
Comment on attachment 64098 [details] typescript from gdb after crash equery uses ekiga [ Searching for packages matching ekiga... ] [ Colour Code : set unset ] [ Legend : Left column (U) - USE flags from make.conf ] [ : Right column (I) - USE flags packages was installed with ] [ Found these USE variables for net-im/ekiga-2.0.1 ] U I - - avahi : Support for the avahi mdns daemon - - dbus : Enable dbus support for anything that needs it (gpsd, gnomemeeting, etc) + + debug : Tells configure and the makefiles to build for debugging. Effects vary across packages, but generally it will at least add -g to CFLAGS. Remember to set FEATURES=nostrip too + + gnome : Adds GNOME support - - ipv6 : Adds support for IP version 6 + + sdl : Adds support for Simple Direct Layer (media library) + + ssl : Adds support for Secure Socket Layer connections
I can not do anything with 20MB of output, sorry. Also, your attachment is full of weird messages, if I was you, I would double-check my builds because they do not look correct at all.
Thanks Sandras for this quick response. I am just a normal gentoo user. no extra-ordinary stuff. I am using the regular tools to constract ekiga,opal and pwlib. ekiga is build with the options specified in my previos post gnome ,sdl,ssl and ovcourse debug. For the most part of the 20Mb it looks like a core dump. pls notice the first lines show ekiga working well. would building it naked give you a better picture? NIv
I don't really know, but Gentoo is often doing weird things. Your OPAL and Ekiga are not built "the standard way".