GNOME Bugzilla – Bug 376771
crash in Ekiga Softphone: j'appelais 500@ekiga.net
Last modified: 2007-01-14 19:01:12 UTC
Version: 2.0.3 What were you doing when the application crashed? j'appelais 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: 109334528 vsize: 0 resident: 109334528 share: 0 rss: 29892608 rss_rlim: 0 CPU usage: start_time: 1163881563 rtime: 0 utime: 3915 stime: 0 cutime:3697 cstime: 0 timeout: 218 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 -1246950624 (LWP 9781)] [New Thread -1266426976 (LWP 9854)] [New Thread -1266160736 (LWP 9825)] [New Thread -1264575584 (LWP 9824)] [New Thread -1265894496 (LWP 9823)] [New Thread -1265628256 (LWP 9815)] [New Thread -1265312864 (LWP 9809)] [New Thread -1264309344 (LWP 9806)] [New Thread -1264043104 (LWP 9805)] [New Thread -1331197024 (LWP 9802)] [New Thread -1322804320 (LWP 9796)] [New Thread -1249240160 (LWP 9786)] [New Thread -1248973920 (LWP 9785)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 87532
Thread 4 (Thread -1264575584 (LWP 9824))
Were you really calling? I mean the backtrace is full of indications you were actually getting out of a call...
That's the same bt than 376190. However, without the debug symbols, it is hard to fix it. *** This bug has been marked as a duplicate of 376190 ***
*** This bug has been marked as a duplicate of 367982 ***