Re: [Ekiga-list] CVS version compiles ok, but problems connecting

2007-02-22 Thread Jure Petrovic
On Thu, 2007-02-22 at 10:21 +0100, Damien Sandras wrote:
> > > Like this :
> > > PTRACE (4, "Hello"); 
> > 
> > As soon as I add such line in g729codec.c, the 
> > codec doesn't get listed anymore in ekiga or 
> > in opalcodecinfo. 
> > 
> 
> Mmmh weird, what about 'cout' instead ? 

Same. The funny thing is, that as soon as
I use g++ (instead of gcc) codec dissappears
from the list. If I use printf, codec gets 
listed, but the function has no effect. 
 
(I took compiler and flags from Makefile and
are same as with the g726)





___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] CVS version compiles ok, but problems connecting

2007-02-22 Thread Damien Sandras
Le jeudi 22 février 2007 à 09:52 +0100, Jure Petrovic a écrit :
> On Wed, 2007-02-21 at 23:27 +0100, Damien Sandras wrote:
> > Use PTRACE and ekiga -d 4.
> > 
> > Like this :
> > PTRACE (4, "Hello"); 
> 
> As soon as I add such line in g729codec.c, the 
> codec doesn't get listed anymore in ekiga or 
> in opalcodecinfo. 
> 

Mmmh weird, what about 'cout' instead ?
-- 
 _  Damien Sandras
(o-  
//\Ekiga Softphone : http://www.ekiga.org/
v_/_  NOVACOM : http://www.novacom.be/
  FOSDEM   : http://www.fosdem.org/
  SIP Phone : sip:[EMAIL PROTECTED]
   


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] CVS version compiles ok, but problems connecting

2007-02-22 Thread Jure Petrovic
On Wed, 2007-02-21 at 23:27 +0100, Damien Sandras wrote:
> Use PTRACE and ekiga -d 4.
> 
> Like this :
> PTRACE (4, "Hello"); 

As soon as I add such line in g729codec.c, the 
codec doesn't get listed anymore in ekiga or 
in opalcodecinfo. 


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] CVS version compiles ok, but problems connecting

2007-02-21 Thread Damien Sandras
Le mercredi 21 février 2007 à 21:39 +0100, Jure Petrovic a écrit :
> On Tue, 2007-02-20 at 16:24 -0800, George Boyd wrote:
> > Thanks Craig, The fix worked fine. :)
> > 
> > I was wondering though if an issue with the video quality in the CVS
> > versions has been discussed. The video quality slider seems to have no
> > effect and the transmitted video is degraded from 2.05.
> > 
> > I guess this would be a pwlib problem?
> > 
> > George 
> 
> 
> Hehe, it works for me too :-)
> 
> Trying to play with codecs, how could I print some messages in the
> console? Classic printf() doesn't work probably because of pwlib...?
> Of course, I run ekiga from console.
> 
> 
Use PTRACE and ekiga -d 4.

Like this :
PTRACE (4, "Hello");
-- 
 _  Damien Sandras
(o-  
//\Ekiga Softphone : http://www.ekiga.org/
v_/_  NOVACOM : http://www.novacom.be/
  FOSDEM   : http://www.fosdem.org/
  SIP Phone : sip:[EMAIL PROTECTED]
   


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] CVS version compiles ok, but problems connecting

2007-02-21 Thread Jure Petrovic
On Tue, 2007-02-20 at 16:24 -0800, George Boyd wrote:
> Thanks Craig, The fix worked fine. :)
> 
> I was wondering though if an issue with the video quality in the CVS
> versions has been discussed. The video quality slider seems to have no
> effect and the transmitted video is degraded from 2.05.
> 
> I guess this would be a pwlib problem?
> 
> George 


Hehe, it works for me too :-)

Trying to play with codecs, how could I print some messages in the
console? Classic printf() doesn't work probably because of pwlib...?
Of course, I run ekiga from console.


Jure

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] CVS version compiles ok, but problems connecting

2007-02-21 Thread Jure Petrovic
On Wed, 2007-02-21 at 08:38 +1100, Craig Southeren wrote:
> This backtrace showed me exactly where I had made my mistake :(
> 
> I've checked in a fix for the problem into the OPAL CVS 


Oh, so it was an opal thing. I would like to try it too, 
but sourceforge cvs seems down. This is the correct adress, 
right? 

cvs -z3
-d:pserver:[EMAIL PROTECTED]:/cvsroot/openh323 co
opal


Jure

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] CVS version compiles ok, but problems connecting

2007-02-21 Thread Damien Sandras
Le mardi 20 février 2007 à 16:12 -0800, George Boyd a écrit :
> >  I've checked in a fix for the problem into the OPAL CVS
> 
> The fix worked fine, Thanks :)
> 
> I was wondering though if an issue with the video quality in the CVS
> versions has been discussed. The video quality slider seems to have no
> effect and the transmitted video is degraded from 2.05.
> 

It is on Craig's TODO list, no worries :)

Indeed, video quality settings, frame rate settings and so on have no
effect currently.
-- 
 _  Damien Sandras
(o-  
//\Ekiga Softphone : http://www.ekiga.org/
v_/_  NOVACOM : http://www.novacom.be/
  FOSDEM   : http://www.fosdem.org/
  SIP Phone : sip:[EMAIL PROTECTED]
   


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] CVS version compiles ok, but problems connecting

2007-02-20 Thread Damien Sandras
Le mercredi 21 février 2007 à 08:38 +1100, Craig Southeren a écrit :
> On Tue, 20 Feb 2007 12:17:07 -0800
> George Boyd <[EMAIL PROTECTED]> wrote:
> 
> > 
> > > the command is thread apply all bt (sorry).
> > > 
> >  I should have known that :)
> > 
> > Here's the output:
> 
> ...deleted
> 
> This backtrace showed me exactly where I had made my mistake :(
> 
> I've checked in a fix for the problem into the OPAL CVS
> 
> My apologies to all for the time wasted
> 

No time has been wasted, it is software development :)

Thanks for the fix !


Damien

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] CVS version compiles ok, but problems connecting

2007-02-20 Thread Craig Southeren
On Tue, 20 Feb 2007 12:17:07 -0800
George Boyd <[EMAIL PROTECTED]> wrote:

> 
> > the command is thread apply all bt (sorry).
> > 
>  I should have known that :)
> 
> Here's the output:

...deleted

This backtrace showed me exactly where I had made my mistake :(

I've checked in a fix for the problem into the OPAL CVS

My apologies to all for the time wasted

   Craig

---
 Craig Southeren  Post Increment – VoIP Consulting and Software
 [EMAIL PROTECTED]   www.postincrement.com.au

 Phone:  +61 243654666  ICQ: #86852844
 Fax:+61 243656905  MSN: [EMAIL PROTECTED]
 Mobile: +61 417231046  Jabber: [EMAIL PROTECTED]

 "It takes a man to suffer ignorance and smile.
  Be yourself, no matter what they say."   Sting


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] CVS version compiles ok, but problems connecting

2007-02-20 Thread Jan Schampera
It's the similar crash as in the other list thread that currently is
discussed (what a good english sentence...).

J.



-- 
Once you've got the perfect hammer, everything looks like a nail.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] CVS version compiles ok, but problems connecting

2007-02-20 Thread George Boyd

> the command is thread apply all bt (sorry).
> 
 I should have known that :)

Here's the output:

(gdb) thread apply all bt

Thread 52 (Thread -1299080304 (LWP 1938)):
#0  0x00131402 in __kernel_vsyscall () at /usr/include/ptclib/http.h:494
#1  0x004be729 in ioctl () at /usr/include/ptclib/http.h:494
#2  0x00efdfec in PVideoInputDevice_V4L2::GetFrameDataNoDelay ()
at /usr/include/ptclib/http.h:494
#3  0x00efe11e in PVideoInputDevice_V4L2::GetFrameData ()
at /usr/include/ptclib/http.h:494
#4  0x024708de in OpalVideoMediaStream::ReadData ()
at /usr/include/ptclib/http.h:494
#5  0x0246f2d5 in OpalMediaStream::ReadPacket ()
at /usr/include/ptclib/http.h:494
#6  0x0247365e in OpalMediaPatch::Main ()
at /usr/include/ptclib/http.h:494
#7  0x02473a2e in OpalMediaPatch::Thread::Main ()
at /usr/include/ptclib/http.h:494
#8  0x02bff83c in PThread::PX_ThreadStart ()
at /usr/include/ptclib/http.h:494
#9  0x0056c3db in start_thread () at /usr/include/ptclib/http.h:494
#10 0x004c626e in clone () at /usr/include/ptclib/http.h:494

Thread 51 (Thread -1298814064 (LWP 1937)):
#0  0x00131402 in __kernel_vsyscall () at /usr/include/ptclib/http.h:494
#1  0x00572aa1 in __lll_mutex_unlock_wake ()
at /usr/include/ptclib/http.h:494
#2  0x0056f7d9 in _L_mutex_unlock_101 ()
at /usr/include/ptclib/http.h:494
---Type  to continue, or q  to quit---
#3  0x0056f440 in __pthread_mutex_unlock_usercnt ()
at /usr/include/ptclib/http.h:494
#4  0x0056f7d0 in pthread_mutex_unlock ()
at /usr/include/ptclib/http.h:494
#5  0x0095d1ca in g_source_attach () at /usr/include/ptclib/http.h:494
#6  0x0095d2bc in g_idle_add_full () at /usr/include/ptclib/http.h:494
#7  0x02c23a30 in PAssertFunc () at /usr/include/ptclib/http.h:494
#8  0x02c16d58 in PAbstractList::Append ()
at /usr/include/ptclib/http.h:494
#9  0x02c0b3b6 in PSocket::SelectList::operator+= ()
at /usr/include/ptclib/http.h:494
#10 0x02c076d3 in PSocket::Select () at /usr/include/ptclib/http.h:494
#11 0x02487d60 in RTP_UDP::ReadData () at /usr/include/ptclib/http.h:494
#12 0x0248c176 in RTP_JitterBuffer::OnReadPacket ()
at /usr/include/ptclib/http.h:494
#13 0x0248e588 in OpalJitterBuffer::OnRead ()
at /usr/include/ptclib/http.h:494
#14 0x0248e9ef in OpalJitterBuffer::JitterThreadMain ()
at /usr/include/ptclib/http.h:494
#15 0x0248ea96 in OpalJitterBuffer::JitterThreadMain_PNotifier::Call ()
at /usr/include/ptclib/http.h:494
#16 0x02c0e28c in PSimpleThread::Main ()
at /usr/include/ptclib/http.h:494
#17 0x02bff83c in PThread::PX_ThreadStart ()
at /usr/include/ptclib/http.h:494
#18 0x0056c3db in start_thread () at /usr/include/ptclib/http.h:494
#19 0x004c626e in clone () at /usr/include/ptclib/http.h:494

---Type  to continue, or q  to quit---
Thread 50 (Thread -1298547824 (LWP 1936)):
#0  0x00131402 in __kernel_vsyscall () at /usr/include/ptclib/http.h:494
#1  0x004bf0d1 in select () at /usr/include/ptclib/http.h:494
#2  0x02c015d2 in PThread::Sleep () at /usr/include/ptclib/http.h:494
#3  0x024736cc in OpalMediaPatch::Main ()
at /usr/include/ptclib/http.h:494
#4  0x02473a2e in OpalMediaPatch::Thread::Main ()
at /usr/include/ptclib/http.h:494
#5  0x02bff83c in PThread::PX_ThreadStart ()
at /usr/include/ptclib/http.h:494
#6  0x0056c3db in start_thread () at /usr/include/ptclib/http.h:494
#7  0x004c626e in clone () at /usr/include/ptclib/http.h:494

Every time it asks ---Type  to continue, or q  to
quit--- If I type enter, it just repeats itself.


Fedora Core 6 Linux
Ekiga Rocks!! One program so many ways to connect!

sip: [EMAIL PROTECTED] (or [EMAIL PROTECTED])
H323: gk.voxgratia.net:1719 geboyd53
SipBroker: *673-617808  -or-  *011-1617808 (alias 617808)
e164: +13606660349 or +882  398265 (linked to ekiga)
Voipbuster: geboyd53 (chat), 13606660349 (telephone)
Forward: 781549
Voxalot: 106153
Gizmo:  17476918163

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] CVS version compiles ok, but problems connecting

2007-02-20 Thread Jure Petrovic
On Tue, 2007-02-20 at 20:22 +0100, Damien Sandras wrote:
> Make sure that your compilation and setup are ok because the crash you
> are reporting is very weird...
> 
> Damien 


My version (2.1.0) from HEAD also crashes with null pointer reference,
when connection gets established! If I run it from console, it prints
out on stdout:

007/02/20 18:36:37.052   1:57.200  SIP Handle...er:969c848 SIP
Could not find SDP media description for Video
2007/02/20 18:36:37.052   1:57.200  SIP Handle...er:969c848 SIP
Could not find SDP media description for Image

Xlib: unexpected async reply (sequence 0x11518)!



___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] CVS version compiles ok, but problems connecting

2007-02-20 Thread Damien Sandras
Le mardi 20 février 2007 à 11:12 -0800, George Boyd a écrit :
> On Tue, 2007-02-20 at 10:53 -0800, George Boyd wrote:
> > When I run gdb ekiga, it doesn't crash, it just stops (but doesn't disappear
> > like it does just running "ekiga"). If I run ekiga on it's
> > own, at the point it crashes I get a window that pops up saying "No
> > Pointer Reference" then it kills itself.
> > 
> 
> I guess what I'm trying to say is that running it under gdb, ekiga
> doesn't kill itself so I can't run "threads apply all bt". When I do,
> it's still running in gdb and it comes back with
> 
> "(gdb) threads apply all bt 
> Undefined command: "threads".  Try "help".
> 
> If I force quit ekiga, gdb says it's still running.
> 
> The problem occurs whenever I try to call out.
> 

the command is thread apply all bt (sorry).

Make sure that your compilation and setup are ok because the crash you
are reporting is very weird...

Damien

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] CVS version compiles ok, but problems connecting

2007-02-20 Thread George Boyd
On Tue, 2007-02-20 at 10:53 -0800, George Boyd wrote:
> When I run gdb ekiga, it doesn't crash, it just stops (but doesn't disappear
> like it does just running "ekiga"). If I run ekiga on it's
> own, at the point it crashes I get a window that pops up saying "No
> Pointer Reference" then it kills itself.
> 

I guess what I'm trying to say is that running it under gdb, ekiga
doesn't kill itself so I can't run "threads apply all bt". When I do,
it's still running in gdb and it comes back with

"(gdb) threads apply all bt 
Undefined command: "threads".  Try "help".

If I force quit ekiga, gdb says it's still running.

The problem occurs whenever I try to call out.

George




___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] CVS version compiles ok, but problems connecting

2007-02-20 Thread George Boyd
When I run gdb ekiga, it doesn't crash, it stops (but doesn't disappear
like it does just running "ekiga") where it errors. If I run ekiga on it
own, at the point it crashes I get a window that pops up saying "No
Pointer Reference" then it kills itself.


(gdb) run
Starting program: /usr/bin/ekiga 
[Thread debugging using libthread_db enabled]
[New Thread -1208731936 (LWP 31376)]
[New Thread -1210831984 (LWP 31438)]
[New Thread -1211098224 (LWP 31439)]
[New Thread -1289057392 (LWP 31468)]
[New Thread -1299547248 (LWP 31469)]
[New Thread -1310037104 (LWP 31470)]
[New Thread -1320526960 (LWP 31471)]
[New Thread -1331016816 (LWP 31472)]
[New Thread -1341506672 (LWP 31473)]
[New Thread -1352410224 (LWP 31476)]
[New Thread -1362900080 (LWP 31479)]
[Thread -1310037104 (LWP 31470) exited]
[Thread -1320526960 (LWP 31471) exited]
[Thread -1331016816 (LWP 31472) exited]
[Thread -1289057392 (LWP 31468) exited]
[Thread -1341506672 (LWP 31473) exited]
[Thread -1299547248 (LWP 31469) exited]
[New Thread -1310409840 (LWP 31516)]
[New Thread -1310676080 (LWP 31517)]
[New Thread -1310942320 (LWP 31518)]
[New Thread -1299547248 (LWP 31519)]
[New Thread -1341506672 (LWP 31520)]
[New Thread -1289057392 (LWP 31521)]
[Thread -1299547248 (LWP 31519) exited]
[Thread -1341506672 (LWP 31520) exited]
[Thread -1289057392 (LWP 31521) exited]
[New Thread -1311470704 (LWP 31525)]
[New Thread -1311736944 (LWP 31526)]
[New Thread -1312003184 (LWP 31527)]
[New Thread -1312269424 (LWP 31528)]
[New Thread -1312535664 (LWP 31529)]
[New Thread -1312801904 (LWP 31531)]
[New Thread -1313068144 (LWP 31532)]
[New Thread -1313334384 (LWP 31533)]
[New Thread -1313600624 (LWP 31535)]
[New Thread -1313866864 (LWP 31537)]
[New Thread -1314133104 (LWP 31538)]
[New Thread -1314399344 (LWP 31539)]
[New Thread -1314665584 (LWP 31540)]
[New Thread -1314931824 (LWP 31542)]
[New Thread -1315198064 (LWP 31543)]
[New Thread -1315464304 (LWP 31544)]
[New Thread -1315730544 (LWP 31545)]
[New Thread -1315996784 (LWP 31548)]
[New Thread -1316263024 (LWP 31549)]
[New Thread -1316529264 (LWP 31550)]
[Thread -1310942320 (LWP 31518) exited]
[New Thread -1310942320 (LWP 31556)]
[New Thread -1316795504 (LWP 31557)]
[Thread -1310942320 (LWP 31556) exited]
[New Thread -1310942320 (LWP 31558)]
   patch.cxx(301)   Patch   Added sink
  from PCM-16
 Clock Rate = 8000
 Frame Time = 8
 Max Bit Rate = 64000
 Max Frame Size = 16
 Needs Jitter = 1
 Rx Frames Per Packet = 240
 Tx Frames Per Packet = 30
to G.711-uLaw-64k
 Clock Rate = 8000
 Frame Time = 8
 Max Bit Rate = 64000
 Max Frame Size = 8
 Needs Jitter = 1
 Rx Frames Per Packet = 240
 Tx Frames Per Packet = 30

   patch.cxx(301)   Patch   Added sink
  from G.711-uLaw-64k
 Clock Rate = 8000
 Frame Time = 8
 Max Bit Rate = 64000
 Max Frame Size = 8
 Needs Jitter = 1
 Rx Frames Per Packet = 240
 Tx Frames Per Packet = 30
to PCM-16
 Clock Rate = 8000
 Frame Time = 8
 Max Bit Rate = 128000
 Max Frame Size = 16
 Needs Jitter = 1
 Rx Frames Per Packet = 240
 Tx Frames Per Packet = 30

[New Thread -1318327408 (LWP 31652)]
   patch.cxx(301)   Patch   Added sink
  from YUV420P
 Adaptive Packet Delay = 1
 Clock Rate = 9
 Dynamic Video Quality = 1
 Encoding Quality = 2
 Frame Height = 144
 Frame Time = 1500
 Frame Width = 176
 Max Bit Rate = 621700
 Target Bit Rate = 64000
to H.261
 Adaptive Packet Delay = 1
 Clock Rate = 9
 Dynamic Video Quality = 1
 Encoding Quality = 2
 Frame Height = 144
 Frame Time = 1500
 Frame Width = 176
 Max Bit Rate = 621700
 Target Bit Rate = 64000
 h323_cifMPI = 4
 h323_qcifMPI = 2

   patch.cxx(301)   Patch   Added sink
  from H.261
 Adaptive Packet Delay = 1
 Clock Rate = 9
 Dynamic Video Quality = 1
 Encoding Quality = 2
 Frame Height = 144
 Frame Time = 1500
 Frame Width = 176
 Max Bit Rate = 621700
 Target Bit Rate = 64000
 h323_cifMPI = 4
 h323_qcifMPI = 2
to YUV420P
 Adaptive Packet Delay = 1
 Clock Rate = 9
 Dynamic Video Quality = 1
 Encoding Quality = 2
 Frame Height = 144
 Frame Time = 3600
 Frame Width = 176
 Max Bit Rate = 30412800
 Target Bit Rate = 64000

[New Thread -1318593648 (LWP 31674)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1318593648 (LWP 31674)]
0x024887a8 in RTP_UDP::WriteData () at /usr/include/ptclib/http.h:494
494 {
(gdb) 




Fedora Core 6 Linux
Ekiga Rocks!! One program so many ways to connect!

sip: [EMAIL PROTECTED] (or [EMAIL

Re: [Ekiga-list] CVS version compiles ok, but problems connecting

2007-02-20 Thread Damien Sandras
Le mardi 20 février 2007 à 04:14 -0800, George Boyd a écrit :
> running the latest snapshots (as of today) of pwlib, opal, and Ekiga
> from a terminal It comes up ok, but when I try to call out, I get this
> error:
> 
> [EMAIL PROTECTED] ~]$ ekiga
>patch.cxx(301)   Patch   Added sink
>   from PCM-16
>  Clock Rate = 8000
>  Frame Time = 8
>  Max Bit Rate = 64000
>  Max Frame Size = 16
>  Needs Jitter = 1
>  Rx Frames Per Packet = 240
>  Tx Frames Per Packet = 30
> to G.711-uLaw-64k
>  Clock Rate = 8000
>  Frame Time = 8
>  Max Bit Rate = 64000
>  Max Frame Size = 8
>  Needs Jitter = 1
>  Rx Frames Per Packet = 240
>  Tx Frames Per Packet = 30
> 
>patch.cxx(301)   Patch   Added sink
>   from G.711-uLaw-64k
>  Clock Rate = 8000
>  Frame Time = 8
>  Max Bit Rate = 64000
>  Max Frame Size = 8
>  Needs Jitter = 1
>  Rx Frames Per Packet = 240
>  Tx Frames Per Packet = 30
> to PCM-16
>  Clock Rate = 8000
>  Frame Time = 8
>  Max Bit Rate = 128000
>  Max Frame Size = 16
>  Needs Jitter = 1
>  Rx Frames Per Packet = 240
>  Tx Frames Per Packet = 30
> 
>patch.cxx(301)   Patch   Added sink
>   from YUV420P
>  Adaptive Packet Delay = 1
>  Clock Rate = 9
>  Dynamic Video Quality = 1
>  Encoding Quality = 6
>  Frame Height = 144
>  Frame Time = 1500
>  Frame Width = 176
>  Max Bit Rate = 621700
>  Target Bit Rate = 64000
> to H.261
>  Adaptive Packet Delay = 1
>  Clock Rate = 9
>  Dynamic Video Quality = 1
>  Encoding Quality = 6
>  Frame Height = 144
>  Frame Time = 1500
>  Frame Width = 176
>  Max Bit Rate = 621700
>  Target Bit Rate = 64000
>  h323_cifMPI = 4
>  h323_qcifMPI = 2
> 
>patch.cxx(301)   Patch   Added sink
>   from H.261
>  Adaptive Packet Delay = 1
>  Clock Rate = 9
>  Dynamic Video Quality = 1
>  Encoding Quality = 6
>  Frame Height = 144
>  Frame Time = 1500
>  Frame Width = 176
>  Max Bit Rate = 621700
>  Target Bit Rate = 64000Xlib: unexpected async reply (sequence
> 0x1e62)!
> Multiple segmentation faults occurred; can't display error dialog
>  h323_cifMPI = 4
>  h323_qcifMPI = 2
> to YUV420P
>  Adaptive Packet Delay = 1
>  Clock Rate = 9
>  Dynamic Video Quality = 1
>  Encoding Quality = 6
>  Frame Height = 144
>  Frame Time = 3600
>  Frame Width = 176
>  Max Bit Rate = 30412800
>  Target Bit Rate = 64000
> 
> Xlib: unexpected async reply (sequence 0x1e62)!
> Multiple segmentation faults occurred; can't display error dialog
> [EMAIL PROTECTED] ~]$ 
> ** (bug-buddy:21176): WARNING **: Couldn't load icon for Open Folder
> 
> ** (bug-buddy:21176): WARNING **: Couldn't load icon for Zapping TV
> Viewer
> ptrace: No such process.
> /home/george/20876: No such file or directory.
> No stack.
> 
> Then Ekiga crashes.

Perhaps CVS is broken ?

Can you try gdb ekiga
type 'run'
and when it crashes, type 'threads apply all bt'
-- 
 _  Damien Sandras
(o-  
//\Ekiga Softphone : http://www.ekiga.org/
v_/_  NOVACOM : http://www.novacom.be/
  FOSDEM   : http://www.fosdem.org/
  SIP Phone : sip:[EMAIL PROTECTED]
   


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list