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 367981 - crash in Ekiga Softphone: Talking to a SIP client ...
crash in Ekiga Softphone: Talking to a SIP client ...
Status: RESOLVED FIXED
Product: ekiga
Classification: Applications
Component: OPAL
2.0.x
Other All
: High critical
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
: 449802 450116 451936 453306 461372 461584 461589 472207 482384 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-10-30 22:45 UTC by Alan Hanley
Modified: 2007-10-29 21:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Alan Hanley 2006-10-30 22:45:12 UTC 
Version: 2.0.3

What were you doing when the application crashed?
Talking to a SIP client (Xlite Version 3.0 Build 34025)using PMCU/H261  and send video to ekiga where it then crashed. The SIP server is Trixbox 1.2.2


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

Memory status: size: 111378432 vsize: 0 resident: 111378432 share: 0 rss: 22200320 rss_rlim: 0
CPU usage: start_time: 1162245147 rtime: 0 utime: 1210 stime: 0 cutime:1110 cstime: 0 timeout: 100 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 -1246841168 (LWP 5033)]
[New Thread -1302180960 (LWP 11380)]
[New Thread -1303323744 (LWP 11379)]
[New Thread -1300235360 (LWP 11378)]
[New Thread -1301914720 (LWP 11377)]
[New Thread -1301075040 (LWP 11376)]
[New Thread -1289405536 (LWP 11370)]
[New Thread -1300501600 (LWP 11358)]
[New Thread -1301648480 (LWP 11357)]
[New Thread -1298850912 (LWP 5168)]
[New Thread -1298584672 (LWP 5167)]
[New Thread -1289139296 (LWP 5066)]
[New Thread -1288873056 (LWP 5065)]
[New Thread -1288606816 (LWP 5060)]
[New Thread -1280214112 (LWP 5050)]
[New Thread -1248765024 (LWP 5043)]
[New Thread -1248498784 (LWP 5042)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 80713

Thread 2 (Thread -1302180960 (LWP 11380))

  • #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 P64Decoder::parse_block
    from /usr/lib/libopal.so.2.2
  • #5 ?? 






Comment 1


Snark





          2006-10-31 05:16:41 UTC
        



Why do you say "send video to ekiga" ? Do you mean you made working audio-only tests first, and it began to fail when you enabled video ?






Comment 2


Alan Hanley





          2006-10-31 05:40:30 UTC
        



My apologies,
what happened was that the call was initiated from the Xlite client on a XP box to the Ekiga Client on my Ubuntu box. Once voice was initiated and working correctly between the two PC's the Xlite client pressed the "Send Video" button. Once that was pressed Ekiga then crashed.
You were spot on, everything was working until video transmission was activated/enabled. One thing to note is that it works perfectly when the video camera is on the Ubuntu/Ekiga system and calls the Xlite/XP system.

Hope this helps and keep up the fantastic work.

Regards,
Alan






Comment 3


Snark





          2006-10-31 07:08:41 UTC
        



Thanks, that will certainly help.






Comment 4


Damien Sandras





          2006-10-31 10:34:23 UTC
        



That's a bug in the P64Decoder of H.261 in OPAL.

Can you get us a backtrace with debug symbols.?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!







Comment 5


Snark





          2007-03-29 15:03:47 UTC
        



Well, does that bug still exist ?






Comment 6


Snark





          2007-06-21 16:33:09 UTC
        



*** Bug 449802 has been marked as a duplicate of this bug. ***






Comment 7


Snark





          2007-06-21 16:37:24 UTC
        



It still lives! Perhaps Luc could have a look?






Comment 8


Snark





          2007-06-22 18:41:09 UTC
        



*** Bug 450116 has been marked as a duplicate of this bug. ***






Comment 9


Snark





          2007-06-28 16:52:36 UTC
        



*** Bug 451936 has been marked as a duplicate of this bug. ***






Comment 10


Damien Sandras





          2007-07-03 07:33:27 UTC
        



*** Bug 453306 has been marked as a duplicate of this bug. ***






Comment 11


Damien Sandras





          2007-07-03 07:34:15 UTC
        



Can somebody provide a stack trace with debug symbols ??






Comment 12


Sebastien Bacher





          2007-07-06 10:27:49 UTC
        



ubuntu bug https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/106556

"#0  0xb6d5b151 in P64Decoder::parse_block () from /usr/lib/libopal.so.2.2




+
Trace
    146084






    

  • 
#1
P64Decoder::decode_block

    
                from
                /usr/lib/libopal.so.2.2

    

    • 

  • 
#2
P64Decoder::decode_mb

    
                from
                /usr/lib/libopal.so.2.2

    

    • 

  • 
#3
P64Decoder::decode

    
                from
                /usr/lib/libopal.so.2.2

    

    • 

  • 
#4
Opal_H261_YUV420P::ConvertFrames

    
                from
                /usr/lib/libopal.so.2.2

    

    • 

  • 
#5
OpalMediaPatch::Sink::WriteFrame

    
                from
                /usr/lib/libopal.so.2.2

    

    • 

  • 
#6
OpalMediaPatch::Main

    
                from
                /usr/lib/libopal.so.2.2

    

    • 

  • 
#7
PThread::PX_ThreadStart

    
                at tlibthrd.cxx
                  line
                  1340

    

    • 

  • 
#8
start_thread

    
                from
                /lib/tls/i686/cmov/libpthread.so.0

    

    • 

  • 
#9
clone

    
                from
                /lib/tls/i686/cmov/libc.so.6"

    

    • 













Comment 13


Sebastien Bacher





          2007-07-06 10:44:37 UTC
        



debug backtrace for the crash:

"#0  0xb6d2d151 in P64Decoder::parse_block (this=0x873d220, blk=0xb269d0b8, mask=0xb269d138)
    at /debug/opal-2.2.3.dfsg/src/codec/vic/p64.cxx:349
349                     blk[0] = qt[(v & 1) ? 0xff : 1];
(gdb) thread apply all bt full





+
Trace
    146088
















Comment 14


Sebastien Bacher





          2007-07-06 10:45:51 UTC
        



"Program terminated with signal 11, Segmentation fault.




+
Trace
    146089






    

  • 
#0
P64Decoder::parse_block

    
                at /debug/opal-2.2.3.dfsg/src/codec/vic/p64.cxx
                  line
                  349

    

    • 

  • 
#0
P64Decoder::parse_block

    
                at /debug/opal-2.2.3.dfsg/src/codec/vic/p64.cxx
                  line
                  349

    

    • 

  • 
#1
P64Decoder::decode_block

    
                at /debug/opal-2.2.3.dfsg/src/codec/vic/p64.cxx
                  line
                  949

    

    • 

  • 
#2
P64Decoder::decode_mb

    
                at /debug/opal-2.2.3.dfsg/src/codec/vic/p64.cxx
                  line
                  1067

    

    • 

  • 
#3
P64Decoder::decode

    
                at /debug/opal-2.2.3.dfsg/src/codec/vic/p64.cxx
                  line
                  1185

    

    • 

  • 
#4
Opal_H261_YUV420P::ConvertFrames

    
                at /debug/opal-2.2.3.dfsg/src/codec/h261codec.cxx
                  line
                  526

    

    • 

  • 
#5
OpalMediaPatch::Sink::WriteFrame

    
                at /debug/opal-2.2.3.dfsg/src/opal/patch.cxx
                  line
                  474

    

    • 

  • 
#6
OpalMediaPatch::Main

    
                at /debug/opal-2.2.3.dfsg/src/opal/patch.cxx
                  line
                  208

    

    • 

  • 
#7
PThread::PX_ThreadStart

    
                at tlibthrd.cxx
                  line
                  1340

    

    • 

  • 
#8
start_thread

    
                from
                /lib/tls/i686/cmov/libpthread.so.0

    

    • 

  • 
#9
clone

    
                from
                /lib/tls/i686/cmov/libc.so.6"

    

    • 













Comment 15


Damien Sandras





          2007-07-06 10:49:57 UTC
        



As you can reproduce it, is there any chance you can see why the variable is invalid ?

That code (H.261) comes from the VIC decoder/encoder, and I have no knowledge about it as most people... (it is very very old).

I would guess adding a simple 'if' somewhere will fix the problem.






Comment 16


Snark





          2007-07-06 11:22:08 UTC
        



If that is that old a code, why do we get reports only now ? :-/







Comment 17


Sebastien Bacher





          2007-07-06 12:17:11 UTC
        



The backtrace comes from the coredump attached to the bug:





+
Trace
    146101






    

  • 
#0
P64Decoder::parse_block

    
                at /debug/opal-2.2.3.dfsg/src/codec/vic/p64.cxx
                  line
                  349

    

    • 







$1 = (short int *) 0x0







Comment 18


Snark





          2007-07-06 12:54:05 UTC
        



I had a look, and qt is a short*, initialized from qt_, which is NULL by default, and initialized as pointing to quant-thingies... I can't say much more :-/






Comment 19


Damien Sandras





          2007-07-06 12:55:32 UTC
        



I have added a guard against a NULL qt. If it does not fix the problem, we will reopen the bug report.






Comment 20


Snark





          2007-07-29 08:06:57 UTC
        



*** Bug 461372 has been marked as a duplicate of this bug. ***






Comment 21


Snark





          2007-07-29 08:07:42 UTC
        



Let's remind for reference : the bug is still in 2.0.9 but shouldn't be in
2.0.10.






Comment 22


Snark





          2007-07-29 21:32:51 UTC
        



*** Bug 461584 has been marked as a duplicate of this bug. ***






Comment 23


Snark





          2007-07-29 21:33:07 UTC
        



*** Bug 461589 has been marked as a duplicate of this bug. ***






Comment 24


Snark





          2007-08-31 13:59:48 UTC
        



*** Bug 472207 has been marked as a duplicate of this bug. ***






Comment 25


Snark





          2007-10-29 21:32:48 UTC
        



*** Bug 482384 has been marked as a duplicate of this bug. ***