Bug 419800 – crash in Ekiga Softphone: I was testing with LPC a...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 419800 - crash in Ekiga Softphone: I was testing with LPC a...


Summary:	crash in Ekiga Softphone: I was testing with LPC a...


Status:	RESOLVED DUPLICATE of bug 398549

Product:	ekiga
Classification:	Applications
Component:	general
Version:	2.0.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Ekiga maintainers
QA Contact:	Ekiga maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-03-18 17:17 UTC by Sébastien Burton
Modified:	2007-03-18 18:39 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Sébastien Burton 2007-03-18 17:17:52 UTC

Version: 2.0.3

What were you doing when the application crashed?
I was testing with LPC active... I don't know what it does... :P


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 108056576 vsize: 0 resident: 108056576 share: 0 rss: 29843456 rss_rlim: 0
CPU usage: start_time: 1174237698 rtime: 0 utime: 4740 stime: 0 cutime:4422 cstime: 0 timeout: 318 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 -1247037776 (LWP 9535)]
[New Thread -1260815456 (LWP 11005)]
[New Thread -1288733792 (LWP 11004)]
[New Thread -1290540128 (LWP 11003)]
[New Thread -1289000032 (LWP 11002)]
[New Thread -1261081696 (LWP 11001)]
[New Thread -1287890016 (LWP 11000)]
[New Thread -1288463456 (LWP 10995)]
[New Thread -1287308384 (LWP 10994)]
[New Thread -1286259808 (LWP 10202)]
[New Thread -1285993568 (LWP 10201)]
[New Thread -1319564384 (LWP 9941)]
[New Thread -1311171680 (LWP 9939)]
[New Thread -1249440864 (LWP 9800)]
[New Thread -1249174624 (LWP 9799)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 119772

Thread 6 (Thread -1261081696 (LWP 11001))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 vparms_
from /usr/lib/libopal.so.2.2
#5 voicin_
from /usr/lib/libopal.so.2.2
#6 analys_
from /usr/lib/libopal.so.2.2
#7 lpc10_encode
from /usr/lib/libopal.so.2.2
#8 Opal_PCM_LPC10::ConvertFrame
from /usr/lib/libopal.so.2.2
#9 ??
#10 ??
#11 ??
#12 PStringStream::~PStringStream
from /usr/lib/libpt.so.1.10.2
#13 OpalFramedTranscoder::ConvertFrame
from /usr/lib/libopal.so.2.2
#14 ??
#15 ??
#16 ??
#17 PAbstractList::SetCurrent
from /usr/lib/libpt.so.1.10.2
#18 OpalFramedTranscoder::Convert
from /usr/lib/libopal.so.2.2
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??

Comment 1 Snark 2007-03-18 17:57:14 UTC

Hmmmm... a crash in the lpc10 encoder now ?!

Is it easy to reproduce ?

Comment 2 Sébastien Burton 2007-03-18 18:12:01 UTC

(In reply to comment #1)
> Is it easy to reproduce ?

No, it does not seems to... On the next time it works without any problems (except the poor speed of my connexion), so I'm not able to reproduce it... And as it is the 2.0.3 version, I don't think it's important...

Comment 3 Damien Sandras 2007-03-18 18:39:42 UTC

It is reproducable, we have dups. It is a long time problem in OPAL :(

*** This bug has been marked as a duplicate of 398549 ***