GNOME Bugzilla – Bug 376190
crash in Ekiga Softphone: Dialing my home number t...
Last modified: 2007-01-14 18:59:58 UTC
Version: 2.0.3 What were you doing when the application crashed? Dialing my home number through a non-default STUN server: stun01.sipphone.com Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 110182400 vsize: 0 resident: 110182400 share: 0 rss: 30179328 rss_rlim: 0 CPU usage: start_time: 1163738057 rtime: 0 utime: 5914 stime: 0 cutime:4150 cstime: 0 timeout: 1764 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 -1247312208 (LWP 10523)] [New Thread -1281475680 (LWP 11468)] [New Thread -1323308128 (LWP 11435)] [New Thread -1281197152 (LWP 11434)] [New Thread -1280930912 (LWP 11408)] [New Thread -1280664672 (LWP 11407)] [New Thread -1280398432 (LWP 10687)] [New Thread -1280132192 (LWP 10654)] [New Thread -1279865952 (LWP 10653)] [New Thread -1279599712 (LWP 10638)] [New Thread -1279284320 (LWP 10637)] [New Thread -1313387616 (LWP 10547)] [New Thread -1313121376 (LWP 10546)] [New Thread -1312855136 (LWP 10543)] [New Thread -1314915424 (LWP 10541)] [New Thread -1249236064 (LWP 10529)] [New Thread -1248969824 (LWP 10528)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 87122
Thread 3 (Thread -1323308128 (LWP 11435))
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! Also, is it reproducable?
This was an automated bug submission. I have not yet reproduced the issue, sorry. If/when I do, I will attempt to gather further stack details.
*** Bug 376771 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 376078 ***
*** This bug has been marked as a duplicate of 367982 ***