GNOME Bugzilla – Bug 393911
crash in Ekiga Softphone: bellen naar 500@ekiga.ne...
Last modified: 2007-01-14 19:12:38 UTC
Version: 2.0.3 What were you doing when the application crashed? bellen naar 500@ekiga.net Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 108380160 vsize: 0 resident: 108380160 share: 0 rss: 31498240 rss_rlim: 0 CPU usage: start_time: 1168181124 rtime: 0 utime: 1235 stime: 0 cutime:1056 cstime: 0 timeout: 179 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 -1247381840 (LWP 7394)] [New Thread -1261433952 (LWP 7442)] [New Thread -1320834144 (LWP 7441)] [New Thread -1261167712 (LWP 7440)] [New Thread -1321858144 (LWP 7417)] [New Thread -1321591904 (LWP 7416)] [New Thread -1320567904 (LWP 7413)] [New Thread -1320301664 (LWP 7412)] [New Thread -1319916640 (LWP 7410)] [New Thread -1311523936 (LWP 7408)] [New Thread -1249592416 (LWP 7397)] [New Thread -1249326176 (LWP 7396)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 100174
Thread 4 (Thread -1261167712 (LWP 7440))
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!
*** This bug has been marked as a duplicate of 367982 ***