GNOME Bugzilla – Bug 376078
crash in Ekiga Softphone: j'essayais de paramétrer...
Last modified: 2007-04-21 14:41:33 UTC
Version: 2.0.3 What were you doing when the application crashed? j'essayais de paramétrer ma webcam philips Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 240549888 vsize: 240549888 resident: 36204544 share: 24137728 rss: 36204544 rss_rlim: -1 CPU usage: start_time: 1163706361 rtime: 408 utime: 368 stime: 40 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/ekiga' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47595814887504 (LWP 10265)] [New Thread 1074538832 (LWP 10610)] [New Thread 1075071312 (LWP 10578)] [New Thread 1074805072 (LWP 10575)] [New Thread 1108375888 (LWP 10293)] [New Thread 1108109648 (LWP 10292)] [New Thread 1124895056 (LWP 10289)] [New Thread 1124628816 (LWP 10280)] [New Thread 1074272592 (LWP 10268)] [New Thread 1074006352 (LWP 10267)] (no debugging symbols found) 0x00002b49c017a7f6 in poll () from /lib/libc.so.6
+ Trace 87039
Thread 2 (Thread 1074538832 (LWP 10610))
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 367982 has been marked as a duplicate of this bug. ***
*** Bug 376190 has been marked as a duplicate of this bug. ***
*** Bug 377152 has been marked as a duplicate of this bug. ***
*** Bug 377189 has been marked as a duplicate of this bug. ***
*** Bug 378712 has been marked as a duplicate of this bug. ***
*** Bug 378809 has been marked as a duplicate of this bug. ***
*** Bug 379015 has been marked as a duplicate of this bug. ***
*** Bug 369540 has been marked as a duplicate of this bug. ***
*** Bug 379782 has been marked as a duplicate of this bug. ***
I have a "Philips 646 webcam", use edgy, and it just works... Notice that I'm still using 2.6.15-27-k7 (ie: my dapper kernel), since the newer edgy kernel just has too many issues (X crash on acpi events, broken wifi driver...).
I see this :
+ Trace 89944
Is it normal that Update is called twice? I really don't see what the problem could be, except a problem in PAbstractDictionary
That just means the problem is in a function called from that function : gdb is unable to name in which because it lacks symbols.
OK, GetNames() could be called from various threads at the same time : - the main Ekiga thread (to present the list of valid device names) - the GMVideoGrabber thread (to display pics from the device) GetNames() was improperly protected by the 'mutex' PMutex : - when Update() is called with names.Update(), it will flush inputDeviceNames - inputDeviceNames could be in PopulateDictionary() due to another Update() leading to the collection being cleared and populated at the same time. Please reopen if the bug still happens with Ekiga 2.0.4 or newer.
*** Bug 382997 has been marked as a duplicate of this bug. ***
*** Bug 384179 has been marked as a duplicate of this bug. ***
*** Bug 386939 has been marked as a duplicate of this bug. ***
*** Bug 386959 has been marked as a duplicate of this bug. ***
*** Bug 388371 has been marked as a duplicate of this bug. ***
*** Bug 386550 has been marked as a duplicate of this bug. ***
*** Bug 389259 has been marked as a duplicate of this bug. ***
*** Bug 370520 has been marked as a duplicate of this bug. ***
*** Bug 392349 has been marked as a duplicate of this bug. ***
It is now fixed in PWLIB HEAD and Phobos. The reason was a race condition when creating the static GetNames. It could be created from 2 separate threads and thus initialize 2 different V4LNames classic instead of unique. Moreover, operations on his dictionary were not thread-safe.
*** Bug 366174 has been marked as a duplicate of this bug. ***
*** Bug 366992 has been marked as a duplicate of this bug. ***
*** Bug 380630 has been marked as a duplicate of this bug. ***
*** Bug 394788 has been marked as a duplicate of this bug. ***
*** Bug 398181 has been marked as a duplicate of this bug. ***
*** Bug 402555 has been marked as a duplicate of this bug. ***
*** Bug 412868 has been marked as a duplicate of this bug. ***
*** Bug 419791 has been marked as a duplicate of this bug. ***
*** Bug 428639 has been marked as a duplicate of this bug. ***
*** Bug 428824 has been marked as a duplicate of this bug. ***
*** Bug 431116 has been marked as a duplicate of this bug. ***
*** Bug 431971 has been marked as a duplicate of this bug. ***