GNOME Bugzilla – Bug 398549
crash in Ekiga Softphone: estableciendo una llamad...
Last modified: 2007-05-10 05:55:17 UTC
Version: 2.0.3 What were you doing when the application crashed? estableciendo una llamada con codec lpc Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 143192064 vsize: 0 resident: 143192064 share: 0 rss: 30842880 rss_rlim: 0 CPU usage: start_time: 1169228041 rtime: 0 utime: 15874 stime: 0 cutime:12283 cstime: 0 timeout: 3591 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/ekiga' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1246894416 (LWP 14214)] [New Thread -1296508000 (LWP 2939)] [New Thread -1295705184 (LWP 2938)] [New Thread -1298138208 (LWP 2937)] [New Thread -1295971424 (LWP 2934)] [New Thread -1296774240 (LWP 2933)] [New Thread -1313395808 (LWP 32040)] [New Thread -1314165856 (LWP 14879)] [New Thread -1312756832 (LWP 14866)] [New Thread -1312490592 (LWP 14865)] [New Thread -1346061408 (LWP 14608)] [New Thread -1337668704 (LWP 14606)] [New Thread -1249121376 (LWP 14472)] [New Thread -1248855136 (LWP 14471)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 103625
Thread 4 (Thread -1298138208 (LWP 2937))
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!
*** Bug 406814 has been marked as a duplicate of this bug. ***
*** Bug 400590 has been marked as a duplicate of this bug. ***
*** Bug 419800 has been marked as a duplicate of this bug. ***
*** Bug 437276 has been marked as a duplicate of this bug. ***
*** Bug 437278 has been marked as a duplicate of this bug. ***