Nabble - Ekiga Dev

Re: Crash with Ekiga Windows rev7315 & Xlite on h263p

2008-12-01T12:38:10Z

When you do the backtrace, maybe it would also help to get an
ekiga -d 4 -u 4
trace output.

Matthias

Von: michel memeteau <michel.memeteau@...>
An: Ekiga development mailing list <ekiga-devel-list@...>
Gesendet: Montag, den 1. Dezember 2008, 21:09:46 Uhr
Betreff: Re: [Ekiga-devel-list] Crash with Ekiga Windows rev7315 & Xlite on h263p

2008/12/1 Matthias Schneider <ma30002000@...>

Hi Michel,
unfortunately I dont see anything wrong in your debug output. Do you think you could get a backtrace?

I will try.

Ekiga seems not to have received any remote video frames yet.

Because Xlite needs manual input for the Xlite video to start and I guess the crash appear before the video gets activated.

BTW, disabling the video ( By disabling H263p for example ) makes the crash disappear.

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: Crash with Ekiga Windows rev7315 & Xlite on h263p

2008-12-01T12:09:46Z

2008/12/1 Matthias Schneider <ma30002000@...>

Hi Michel,
unfortunately I dont see anything wrong in your debug output. Do you think you could get a backtrace?

I will try.

Ekiga seems not to have received any remote video frames yet.

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: Crash with Ekiga Windows rev7315 & Xlite on h263p

2008-12-01T10:48:25Z

Hi Michel,
unfortunately I dont see anything wrong in your debug output. Do you think you could get a backtrace?

http://wiki.ekiga.org/index.php/Debugging_Ekiga

Ekiga seems not to have received any remote video frames yet.

Thanks in advance.
Matthias

Von: michel memeteau <michel.memeteau@...>
An: Ekiga development mailing list <ekiga-devel-list@...>
Gesendet: Montag, den 1. Dezember 2008, 10:03:59 Uhr
Betreff: [Ekiga-devel-list] Crash with Ekiga Windows rev7315 & Xlite on h263p

Hi , I quickly tested latest Ekiga Windows beta with latest Xlite v 3.0 ( Mac) .

As soon as Ekiga tried to open the video (remote it seems) Ekiga crashed.

I grabbed a debug trace so I'd like to have your input about the possible reasons.

trace can be grabbed from http://pastebin.com/f56c4760d

My Nat config is pretty non-sense as the call is between two endpoints behind the same nat and avahi can't be used.

i'm almost I used Video with Xlite Few months ago while Ekiga Linux Was still SVN 2.9. I will test with Linux as well Soon.

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Crash with Ekiga Windows rev7315 & Xlite on h263p

2008-12-01T01:03:59Z

Hi , I quickly tested latest Ekiga Windows beta with latest Xlite v 3.0 ( Mac) .

As soon as Ekiga tried to open the video (remote it seems) Ekiga crashed.

I grabbed a debug trace so I'd like to have your input about the possible reasons.

trace can be grabbed from http://pastebin.com/f56c4760d

My Nat config is pretty non-sense as the call is between two endpoints behind the same nat and avahi can't be used.

i'm almost I used Video with Xlite Few months ago while Ekiga Linux Was still SVN 2.9. I will test with Linux as well Soon.

--
%<------------------------------------------------------->%
Michel memeteau
Blog 0.2 : http://memeteau.free.fr
Fixe : 0974763294 Mobile : 0624808051
VOIP | Visio: sip%3Afreechelmi@...
jabber/GTalk : xmpp%3Afreechelmi@...

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: [Kamailio-Users] Webx-SER: a new project to give kamailio users a web interface (like Serweb was)

2008-11-30T12:39:45Z

Le dimanche 30 novembre 2008 à 21:58 +0200, Daniel-Constantin Mierla a
écrit :
> thank you for your work and this project. Are there any screenshots
> available?
>

What you see in action here:
https://www.ekiga.net/ (the backend is kamailio)

Is what you get from here:
http://webxser.tuxfamily.org/

> A web interface is something very important in x-ser ecosystem. I
> personally want to direct effort in this direction, to help
> developers
> of this kind of applications, to integrate better with
> kamailio/openser
> and sip-router -- feel free to approach me.

That's very kind from you. I do this for fun on my spare time for some
friends of mine (see http://www.ekiga.org ). My job is teacher in
primary school. I work for the french state.

Anyone willing to join the effort is welcome.

Best regards,
Yannick Defais

>
> Cheers,
> Daniel
--
Me joindre en téléphonie IP / vidéoconférence ?
sip:yannick@...
Logiciel de VoIP Ekiga : http://www.ekiga.org
http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: [Ekiga-list] Webx-SER: a new project to give kamailio users a web interface (like Serweb was)

2008-11-29T08:39:23Z

Le samedi 29 novembre 2008 à 16:41 +0100, yannick a écrit :

> Hello,
>
> I started a project to give users of Kamailio server a web interface to
> register and manage their datas. It was inspired by a need of the
> Ekiga.net platform ( https://www.ekiga.net ) to allow users register
> like they were able to do when Ekiga.net was using SER and Serweb.
>
> I called this software Webx-SER.
>
> Webx-SER feature now:
> * Registration of accounts to kamailio
> * Password reminder
> * Changing password
>
> Technically, Webx-SER use PHP and MySQL. It has a cache system for
> common non-interactives pages, a template system to split HTML from PHP
> and a captcha system to prevent bots. Some work has been put in managing
> forms to make it user-friendly.
>
> The licence is GPL 3 or higher.
>
> Webx-SER is actually used on https://www.ekiga.net
>
> There is a web site for Webx-SER developments, including users and
> devels mailing-list, bug tracking system, source tarball releases and
> GIT repository for source code here:
> http://webxser.tuxfamily.org/
>
> Feedback, comments, help in coding will be warmly welcome.
>
> I also want to thanks Damien Sandras and Jan Schampera for their help,
> support and inspiration.

Big thanks go to you for the real work :-)
--
_ Damien Sandras
(o-
//\ Ekiga Softphone : http://www.ekiga.org/
v_/_ Be IP : http://www.beip.be/
FOSDEM : http://www.fosdem.org/
SIP Phone : sip:dsandras@...

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Webx-SER: a new project to give kamailio users a web interface (like Serweb was)

2008-11-29T07:41:29Z

Hello,

I started a project to give users of Kamailio server a web interface to
register and manage their datas. It was inspired by a need of the
Ekiga.net platform ( https://www.ekiga.net ) to allow users register
like they were able to do when Ekiga.net was using SER and Serweb.

I called this software Webx-SER.

Webx-SER feature now:
* Registration of accounts to kamailio
* Password reminder
* Changing password

Technically, Webx-SER use PHP and MySQL. It has a cache system for
common non-interactives pages, a template system to split HTML from PHP
and a captcha system to prevent bots. Some work has been put in managing
forms to make it user-friendly.

The licence is GPL 3 or higher.

Webx-SER is actually used on https://www.ekiga.net

There is a web site for Webx-SER developments, including users and
devels mailing-list, bug tracking system, source tarball releases and
GIT repository for source code here:
http://webxser.tuxfamily.org/

Feedback, comments, help in coding will be warmly welcome.

I also want to thanks Damien Sandras and Jan Schampera for their help,
support and inspiration.

Best regards,
Yannick Defais

--
Me joindre en téléphonie IP / vidéoconférence ?
sip:yannick@...
Logiciel de VoIP Ekiga : http://www.ekiga.org
http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: svn trunk versioning

2008-11-26T02:29:24Z

Le mardi 25 novembre 2008 à 13:49 +0000, Peter Robinson a écrit :
> Hi All,
>
> Quick query, shouldn't the version in ekiga trunk be pushed to 3.1.0
> or something higher than the current stable? Its currently sitting at
> 3.0.0 still according to configure.ac

It was done at one place, but not the other one. Should be ok now.
--
_ Damien Sandras
(o-
//\ Ekiga Softphone : http://www.ekiga.org/
v_/_ Be IP : http://www.beip.be/
FOSDEM : http://www.fosdem.org/
SIP Phone : sip:dsandras@...

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: Ekiga DBUS-Documentation

2008-11-25T10:54:53Z

Heiser Michael a écrit :
> Is it possible to find some documentation about the DBUS-Integration for Ekiga and perhaps some code snippets?
>
> In the sources of Ekiga itself I only found the HAL-DBUS integration. But I want to know how to integrate selfwritten DBUS-Code into Ekiga.

For 2.0.x, the documentation is in the doc/ directory if I remember well.

For 3.0.x, the DBUS code doesn't work anymore, as there was so little
interest in it...

Snark
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Ekiga DBUS-Documentation

2008-11-25T06:48:49Z

Dear Ekiga Team,

Is it possible to find some documentation about the DBUS-Integration for Ekiga and perhaps some code snippets?

In the sources of Ekiga itself I only found the HAL-DBUS integration. But I want to know how to integrate selfwritten DBUS-Code into Ekiga.

Please let me know.

Thanks from Germany

Michael

[Michael Heiser.vcf]

BEGIN:VCARD VERSION:2.1 X-MS-SIGNATURE:YES N;LANGUAGE=de:Heiser;Michael FN:Michael Heiser ORG:Albstadt-Sigmaringen University TITLE:Student Kommunikations- und Softwaretechnik TEL;CELL;VOICE:+49 1741732424 X-MS-OL-DEFAULT-POSTAL-ADDRESS:0 EMAIL;PREF;INTERNET:heisermi@... X-MS-OL-DESIGN;CHARSET=utf-8:<card xmlns="http://schemas.microsoft.com/office/outlook/12/electronicbusinesscards" ver="1.0" layout="left" bgcolor="ffffff"><img xmlns="" align="fit" area="16" use="cardpicture"/><fld xmlns="" prop="name" align="left" dir="ltr" style="b" color="000000" size="10"/><fld xmlns="" prop="org" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="title" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="telcell" align="left" dir="ltr" color="000000" size="8"><label align="right" color="626262">Mobiltelefon</label></fld><fld xmlns="" prop="email" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/></card> REV:20081125T144743Z END:VCARD

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

svn trunk versioning

2008-11-25T05:49:14Z

Hi All,

Quick query, shouldn't the version in ekiga trunk be pushed to 3.1.0
or something higher than the current stable? Its currently sitting at
3.0.0 still according to configure.ac

Peter
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: Call for testing our new ekiga.net platform

2008-11-22T15:00:38Z

On Sat, Nov 22, 2008 at 5:35 PM, Damien Sandras <dsandras@...> wrote:

> > Do you think it could be useful ?
>
> I'm subscribing for an account.

They declined it. I'm most probably fake...

You need to subscribe as an individual weirdly. , you can contact them on Jabber , there is no reason they refuse you.

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: Call for testing our new ekiga.net platform

2008-11-22T08:35:33Z

Le samedi 22 novembre 2008 à 16:36 +0100, Damien Sandras a écrit :

> Le samedi 22 novembre 2008 à 15:05 +0100, michel memeteau a écrit :
> > On Wed, Nov 12, 2008 at 9:37 AM, michel memeteau
> > <michel.memeteau@...> wrote:
> > Congrats To evryone involved for the new interface !
> >
> >
> > Suggestion : Maybe donations could be used to buy a
> > certificate for 20 $/Year ?
> >
> >
> > IE7 / Chrome and FF3 security message make the newbie user
> > think usually the website is dead ( experience inside )
> >
> >
> > Im still wondering if I can suggest https://ekiga.net to newbies that
> > will get the Warning on Firefox3 about selfsigned certificate.
> >
> > As a temporary workaround, StartSSL Gives Free SSL certificate fo a
> > Domain that works on all browsers except IE. this a a good
> > compromise , We can tell people " It seems not working becasue you are
> > using IE7 , Use Firefox" .
> >
> > Do you think it could be useful ?
>
> I'm subscribing for an account.

They declined it. I'm most probably fake...
--
_ Damien Sandras
(o-
//\ Ekiga Softphone : http://www.ekiga.org/
v_/_ Be IP : http://www.beip.be/
FOSDEM : http://www.fosdem.org/
SIP Phone : sip:dsandras@...

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: Call for testing our new ekiga.net platform

2008-11-22T07:36:43Z

Le samedi 22 novembre 2008 à 15:05 +0100, michel memeteau a écrit :

> On Wed, Nov 12, 2008 at 9:37 AM, michel memeteau
> <michel.memeteau@...> wrote:
> Congrats To evryone involved for the new interface !
>
>
> Suggestion : Maybe donations could be used to buy a
> certificate for 20 $/Year ?
>
>
> IE7 / Chrome and FF3 security message make the newbie user
> think usually the website is dead ( experience inside )
>
>
> Im still wondering if I can suggest https://ekiga.net to newbies that
> will get the Warning on Firefox3 about selfsigned certificate.
>
> As a temporary workaround, StartSSL Gives Free SSL certificate fo a
> Domain that works on all browsers except IE. this a a good
> compromise , We can tell people " It seems not working becasue you are
> using IE7 , Use Firefox" .
>
> Do you think it could be useful ?

I'm subscribing for an account.
--
_ Damien Sandras
(o-
//\ Ekiga Softphone : http://www.ekiga.org/
v_/_ Be IP : http://www.beip.be/
FOSDEM : http://www.fosdem.org/
SIP Phone : sip:dsandras@...

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: Call for testing our new ekiga.net platform

2008-11-22T06:05:56Z

On Wed, Nov 12, 2008 at 9:37 AM, michel memeteau <michel.memeteau@...> wrote:

Congrats To evryone involved for the new interface !

Suggestion : Maybe donations could be used to buy a certificate for 20 $/Year ?

IE7 / Chrome and FF3 security message make the newbie user think usually the website is dead ( experience inside )

Im still wondering if I can suggest https://ekiga.net to newbies that will get the Warning on Firefox3 about selfsigned certificate.

As a temporary workaround, StartSSL Gives Free SSL certificate fo a Domain that works on all browsers except IE. this a a good compromise , We can tell people " It seems not working becasue you are using IE7 , Use Firefox" .

Do you think it could be useful ?

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Debian packages

2008-11-20T13:00:02Z

Hi,

This email summarises information about debian packages on ekiga Web
site, http://snapshots.ekiga.net. This site provides three kinds of
packages:

1. one package for non-free codecs, to be installed together with
official debian packages currently from experimental

2. snapshot packages from the stable branch (which should be more stable
than official debian's ones)

3. snaphots packages from the trunk (unstable), not yet available

More information can be found at http://snapshots.ekiga.net.

Cheers,
--
Eugen Dedu
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: I found a bug... finally!

2008-11-20T05:15:54Z

Julien Puydt a écrit :
> There is definitely a problem with gmref_ptr, but I still don't know
> which :-/

I kicked all uses of gmref_inc/gmref_dec out of the GUI, and it doesn't
crash anymore. Sigh...

Snark
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: I found a bug... finally!

2008-11-20T04:51:37Z

Julien Puydt a écrit :

> Hi,
>
> after days of fight, I managed to get a simpler program to crash like
> ekiga yesterday evening. This night, I made that program simpler.
>
> You'll find attached what's needed to reproduce the crash. You'll need
> to unpack the tarball somewhere, and modify the EKIGA_DIR line to point
> to your fresh ekiga sources ; then :
> make copy (gets some files from ekiga)
> make patch (will kick some pieces of code out and use
> std::tr1::shared_ptr instead)
> make (will build a mini-ekiga)
>
> After that, running "valgrind ./ekiga" should get you a crash.
>
> It is a bug in sigc++, as far as I can tell.
>
> I'm not 100% sure it was the only bug : but that will have to wait until
> that one is fixed/got around.

Sigh :-(

It's not a crash, it's just something valgrind doesn't like...

There is definitely a problem with gmref_ptr, but I still don't know
which :-/

Snark
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

I found a bug... finally!

2008-11-18T17:47:56Z

Hi,

after days of fight, I managed to get a simpler program to crash like
ekiga yesterday evening. This night, I made that program simpler.

You'll find attached what's needed to reproduce the crash. You'll need
to unpack the tarball somewhere, and modify the EKIGA_DIR line to point
to your fresh ekiga sources ; then :
make copy (gets some files from ekiga)
make patch (will kick some pieces of code out and use
std::tr1::shared_ptr instead)
make (will build a mini-ekiga)

After that, running "valgrind ./ekiga" should get you a crash.

It is a bug in sigc++, as far as I can tell.

I'm not 100% sure it was the only bug : but that will have to wait until
that one is fixed/got around.

Volunteers, get that bug dead!

Snark

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

gmref-crashy.tar.bz2 (2K) Download Attachment

Re: Error compiling

2008-11-18T00:50:39Z

Le mardi 18 novembre 2008 à 09:36 +0100, Eugen Dedu a écrit :

> Damien Sandras wrote:
> > Le lundi 17 novembre 2008 à 22:03 +0100, Eugen Dedu a écrit :
> >> With stable branches, I have 2 compilation errors in ekiga:
> >>
> >> g++ -DHAVE_CONFIG_H -I. -I..
> >> -I../lib -I../lib/gmconf -I../lib/toolbox -I../lib/gui -I../lib/engine/
> >> -I../lib/engine/gui/gtk-frontend -I../lib/engine/account/skel
> >> -I../lib/engine/addressbook/skel -I../lib/engine/chat/skel
> >> -I../lib/engine/presence/skel -I../lib/engine/protocol/skel
> >> -I../lib/engine/protocol/sip -I../lib/engine/videooutput/skel
> >> -I../lib/engine/videoinput/skel -I../lib/engine/audioinput/skel
> >> -I../lib/engine/audiooutput/skel -I../lib/engine/hal/skel
> >> -I../lib/engine/framework -I../lib/engine/gui/gtk-core -I../src
> >> -I../src/clients/ -I../src/components/ -I../src/devices/
> >> -I../src/endpoints/ -I../src/gui/ -I.. -DSCHEMA_AGE=62
> >> -I../lib/engine/videooutput/common -I../lib/engine/videooutput/x
> >> -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include
> >> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0
> >> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
> >> -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12
> >> -I/usr/include/pixman-1 -pthread -I/usr/include/glib-2.0
> >> -I/usr/lib/glib-2.0/include -DORBIT2=1 -pthread -D_REENTRANT
> >> -I/usr/include/libgnome-2.0 -I/usr/include/orbit-2.0
> >> -I/usr/include/gconf/2 -I/usr/include/gnome-vfs-2.0
> >> -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/glib-2.0
> >> -I/usr/lib/glib-2.0/include -I/usr/include/libbonobo-2.0
> >> -I/usr/include/bonobo-activation-2.0 -I/usr/include/libgnomeui-2.0
> >> -I/usr/include/libart-2.0 -I/usr/include/gnome-keyring-1
> >> -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0
> >> -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/include/pango-1.0
> >> -I/usr/include/gail-1.0 -I/usr/include/freetype2 -I/usr/include/atk-1.0
> >> -I/usr/lib/gtk-2.0/include -I/usr/include/cairo -I/usr/include/directfb
> >> -I/usr/include/libpng12 -I/usr/include/pixman-1
> >> -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include
> >> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DPTRACING=1
> >> -D_REENTRANT -D_GNU_SOURCE=1 -fno-exceptions -I/usr/include/opal
> >> -I/usr/include/SDL -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1
> >> -fno-exceptions -I/usr/include/SDL -I/usr/include/sigc++-2.0
> >> -I/usr/lib/sigc++-2.0/include -I/usr/include/libxml2 -D_REENTRANT
> >> -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0
> >> -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0
> >> -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include
> >> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0
> >> -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12
> >> -I/usr/include/pixman-1 -Wall -g -O2 -Wall -Wextra -Winit-self
> >> -Wswitch-default -Wswitch-enum -Wstrict-aliasing=2 -Wfloat-equal
> >> -Wshadow -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o `test -f
> >> 'gui/main.cpp' || echo './'`gui/main.cpp
> >> gui/statusmenu.h: In function ‘GtkWidget*
> >> gm_mw_init_status_toolbar(GtkWidget*)’:
> >> gui/statusmenu.h:86: error: too few arguments to function ‘GtkWidget*
> >> status_menu_new(Ekiga::ServiceCore&)’
> >> gui/main.cpp:1708: error: at this point in file
> >> gui/main.cpp:1709: error: ‘struct _GmMainWindow’ has no member named ‘priv’
> >> gui/main.cpp:1709: error: ‘struct _GmMainWindow’ has no member named ‘priv’
> >> make[4]: *** [main.o] Error 1
> >> make[4]: Leaving directory `/home/dedu/softs/ekiga/ekiga/src'
> >
> > Oups...
> >
> > I can not test, but I think it is fixed.
>
>
> mv -f .deps/assistant.Tpo .deps/assistant.Po
> g++ -DHAVE_CONFIG_H -I. -I.. -I../lib -I../lib/gmconf -I../lib/toolbox
> -I../lib/gui -I../lib/eng
> ine/ -I../lib/engine/gui/gtk-frontend -I../lib/engine/account/skel
> -I../lib/engine/addressbook/s
> kel -I../lib/engine/chat/skel -I../lib/engine/presence/skel
> -I../lib/engine/protocol/skel -I../l
> ib/engine/protocol/sip -I../lib/engine/videooutput/skel
> -I../lib/engine/videoinput/skel -I../lib
> /engine/audioinput/skel -I../lib/engine/audiooutput/skel
> -I../lib/engine/hal/skel -I../lib/engin
> e/framework -I../lib/engine/gui/gtk-core -I../src -I../src/clients/
> -I../src/components/ -I../sr
> c/devices/ -I../src/endpoints/ -I../src/gui/ -I.. -DSCHEMA_AGE=62
> -I../lib/engine/videooutput/c
> 2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libbonobo-2.0
> -I/usr/include/bonobo-activation-2.0 -I/usr/include/libgnomeui-2.0
> -I/usr/include/libart-2.0 -I/usr/include/gnome-keyring-1
> -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0
> -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/include/pango-1.0
> -I/usr/include/gail-1.0 -I/usr/include/freetype2 -I/usr/include/atk-1.0
> -I/usr/lib/gtk-2.0/include -I/usr/include/cairo -I/usr/include/directfb
> -I/usr/include/libpng12 -I/usr/include/pixman-1
> -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DPTRACING=1
> -D_REENTRANT -D_GNU_SOURCE=1 -fno-exceptions -I/usr/include/opal
> -I/usr/include/SDL -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1
> -fno-exceptions -I/usr/include/SDL -I/usr/include/sigc++-2.0
> -I/usr/lib/sigc++-2.0/include -I/usr/include/libxml2 -D_REENTRANT
> -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0
> -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0
> -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0
> -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12
> -I/usr/include/pixman-1 -Wall -g -O2 -Wall -Wextra -Winit-self
> -Wswitch-default -Wswitch-enum -Wstrict-aliasing=2 -Wfloat-equal
> -Wshadow -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o `test -f
> 'gui/main.cpp' || echo './'`gui/main.cpp
> gui/main.cpp: In function ‘GtkWidget*
> gm_mw_init_status_toolbar(GtkWidget*)’:
> gui/main.cpp:1708: error: no match for ‘operator*’ in
> ‘*mw->_GmMainWindow::core’
> make[4]: *** [main.o] Error 1
> make[4]: Leaving directory `/home/dedu/softs/ekiga/ekiga/src'

Is it better if you replace *mw->core by mw->core at this place ?
--
_ Damien Sandras
(o-
//\ Ekiga Softphone : http://www.ekiga.org/
v_/_ Be IP : http://www.beip.be/
FOSDEM : http://www.fosdem.org/
SIP Phone : sip:dsandras@...

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: Error compiling

2008-11-18T00:36:30Z

Damien Sandras wrote:

> Le lundi 17 novembre 2008 à 22:03 +0100, Eugen Dedu a écrit :
>> With stable branches, I have 2 compilation errors in ekiga:
>>
>> g++ -DHAVE_CONFIG_H -I. -I..
>> -I../lib -I../lib/gmconf -I../lib/toolbox -I../lib/gui -I../lib/engine/
>> -I../lib/engine/gui/gtk-frontend -I../lib/engine/account/skel
>> -I../lib/engine/addressbook/skel -I../lib/engine/chat/skel
>> -I../lib/engine/presence/skel -I../lib/engine/protocol/skel
>> -I../lib/engine/protocol/sip -I../lib/engine/videooutput/skel
>> -I../lib/engine/videoinput/skel -I../lib/engine/audioinput/skel
>> -I../lib/engine/audiooutput/skel -I../lib/engine/hal/skel
>> -I../lib/engine/framework -I../lib/engine/gui/gtk-core -I../src
>> -I../src/clients/ -I../src/components/ -I../src/devices/
>> -I../src/endpoints/ -I../src/gui/ -I.. -DSCHEMA_AGE=62
>> -I../lib/engine/videooutput/common -I../lib/engine/videooutput/x
>> -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include
>> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0
>> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
>> -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12
>> -I/usr/include/pixman-1 -pthread -I/usr/include/glib-2.0
>> -I/usr/lib/glib-2.0/include -DORBIT2=1 -pthread -D_REENTRANT
>> -I/usr/include/libgnome-2.0 -I/usr/include/orbit-2.0
>> -I/usr/include/gconf/2 -I/usr/include/gnome-vfs-2.0
>> -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/glib-2.0
>> -I/usr/lib/glib-2.0/include -I/usr/include/libbonobo-2.0
>> -I/usr/include/bonobo-activation-2.0 -I/usr/include/libgnomeui-2.0
>> -I/usr/include/libart-2.0 -I/usr/include/gnome-keyring-1
>> -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0
>> -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/include/pango-1.0
>> -I/usr/include/gail-1.0 -I/usr/include/freetype2 -I/usr/include/atk-1.0
>> -I/usr/lib/gtk-2.0/include -I/usr/include/cairo -I/usr/include/directfb
>> -I/usr/include/libpng12 -I/usr/include/pixman-1
>> -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include
>> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DPTRACING=1
>> -D_REENTRANT -D_GNU_SOURCE=1 -fno-exceptions -I/usr/include/opal
>> -I/usr/include/SDL -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1
>> -fno-exceptions -I/usr/include/SDL -I/usr/include/sigc++-2.0
>> -I/usr/lib/sigc++-2.0/include -I/usr/include/libxml2 -D_REENTRANT
>> -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0
>> -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0
>> -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include
>> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0
>> -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12
>> -I/usr/include/pixman-1 -Wall -g -O2 -Wall -Wextra -Winit-self
>> -Wswitch-default -Wswitch-enum -Wstrict-aliasing=2 -Wfloat-equal
>> -Wshadow -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o `test -f
>> 'gui/main.cpp' || echo './'`gui/main.cpp
>> gui/statusmenu.h: In function ‘GtkWidget*
>> gm_mw_init_status_toolbar(GtkWidget*)’:
>> gui/statusmenu.h:86: error: too few arguments to function ‘GtkWidget*
>> status_menu_new(Ekiga::ServiceCore&)’
>> gui/main.cpp:1708: error: at this point in file
>> gui/main.cpp:1709: error: ‘struct _GmMainWindow’ has no member named ‘priv’
>> gui/main.cpp:1709: error: ‘struct _GmMainWindow’ has no member named ‘priv’
>> make[4]: *** [main.o] Error 1
>> make[4]: Leaving directory `/home/dedu/softs/ekiga/ekiga/src'
>
> Oups...
>
> I can not test, but I think it is fixed.

mv -f .deps/assistant.Tpo .deps/assistant.Po
g++ -DHAVE_CONFIG_H -I. -I.. -I../lib -I../lib/gmconf -I../lib/toolbox
-I../lib/gui -I../lib/eng
ine/ -I../lib/engine/gui/gtk-frontend -I../lib/engine/account/skel
-I../lib/engine/addressbook/s
kel -I../lib/engine/chat/skel -I../lib/engine/presence/skel
-I../lib/engine/protocol/skel -I../l
ib/engine/protocol/sip -I../lib/engine/videooutput/skel
-I../lib/engine/videoinput/skel -I../lib
/engine/audioinput/skel -I../lib/engine/audiooutput/skel
-I../lib/engine/hal/skel -I../lib/engin
e/framework -I../lib/engine/gui/gtk-core -I../src -I../src/clients/
-I../src/components/ -I../sr
c/devices/ -I../src/endpoints/ -I../src/gui/ -I.. -DSCHEMA_AGE=62
-I../lib/engine/videooutput/c
2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libbonobo-2.0
-I/usr/include/bonobo-activation-2.0 -I/usr/include/libgnomeui-2.0
-I/usr/include/libart-2.0 -I/usr/include/gnome-keyring-1
-I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0
-I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/include/pango-1.0
-I/usr/include/gail-1.0 -I/usr/include/freetype2 -I/usr/include/atk-1.0
-I/usr/lib/gtk-2.0/include -I/usr/include/cairo -I/usr/include/directfb
-I/usr/include/libpng12 -I/usr/include/pixman-1
-I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DPTRACING=1
-D_REENTRANT -D_GNU_SOURCE=1 -fno-exceptions -I/usr/include/opal
-I/usr/include/SDL -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1
-fno-exceptions -I/usr/include/SDL -I/usr/include/sigc++-2.0
-I/usr/lib/sigc++-2.0/include -I/usr/include/libxml2 -D_REENTRANT
-I/usr/include/gtk-2.0 -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0
-I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0
-I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12
-I/usr/include/pixman-1 -Wall -g -O2 -Wall -Wextra -Winit-self
-Wswitch-default -Wswitch-enum -Wstrict-aliasing=2 -Wfloat-equal
-Wshadow -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o `test -f
'gui/main.cpp' || echo './'`gui/main.cpp
gui/main.cpp: In function ‘GtkWidget*
gm_mw_init_status_toolbar(GtkWidget*)’:
gui/main.cpp:1708: error: no match for ‘operator*’ in
‘*mw->_GmMainWindow::core’
make[4]: *** [main.o] Error 1
make[4]: Leaving directory `/home/dedu/softs/ekiga/ekiga/src'

--
Eugen
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: Error compiling

2008-11-17T13:27:55Z

Le lundi 17 novembre 2008 à 22:03 +0100, Eugen Dedu a écrit :

> With stable branches, I have 2 compilation errors in ekiga:
>
> g++ -DHAVE_CONFIG_H -I. -I..
> -I../lib -I../lib/gmconf -I../lib/toolbox -I../lib/gui -I../lib/engine/
> -I../lib/engine/gui/gtk-frontend -I../lib/engine/account/skel
> -I../lib/engine/addressbook/skel -I../lib/engine/chat/skel
> -I../lib/engine/presence/skel -I../lib/engine/protocol/skel
> -I../lib/engine/protocol/sip -I../lib/engine/videooutput/skel
> -I../lib/engine/videoinput/skel -I../lib/engine/audioinput/skel
> -I../lib/engine/audiooutput/skel -I../lib/engine/hal/skel
> -I../lib/engine/framework -I../lib/engine/gui/gtk-core -I../src
> -I../src/clients/ -I../src/components/ -I../src/devices/
> -I../src/endpoints/ -I../src/gui/ -I.. -DSCHEMA_AGE=62
> -I../lib/engine/videooutput/common -I../lib/engine/videooutput/x
> -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
> -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12
> -I/usr/include/pixman-1 -pthread -I/usr/include/glib-2.0
> -I/usr/lib/glib-2.0/include -DORBIT2=1 -pthread -D_REENTRANT
> -I/usr/include/libgnome-2.0 -I/usr/include/orbit-2.0
> -I/usr/include/gconf/2 -I/usr/include/gnome-vfs-2.0
> -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/glib-2.0
> -I/usr/lib/glib-2.0/include -I/usr/include/libbonobo-2.0
> -I/usr/include/bonobo-activation-2.0 -I/usr/include/libgnomeui-2.0
> -I/usr/include/libart-2.0 -I/usr/include/gnome-keyring-1
> -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0
> -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/include/pango-1.0
> -I/usr/include/gail-1.0 -I/usr/include/freetype2 -I/usr/include/atk-1.0
> -I/usr/lib/gtk-2.0/include -I/usr/include/cairo -I/usr/include/directfb
> -I/usr/include/libpng12 -I/usr/include/pixman-1
> -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DPTRACING=1
> -D_REENTRANT -D_GNU_SOURCE=1 -fno-exceptions -I/usr/include/opal
> -I/usr/include/SDL -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1
> -fno-exceptions -I/usr/include/SDL -I/usr/include/sigc++-2.0
> -I/usr/lib/sigc++-2.0/include -I/usr/include/libxml2 -D_REENTRANT
> -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0
> -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0
> -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0
> -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12
> -I/usr/include/pixman-1 -Wall -g -O2 -Wall -Wextra -Winit-self
> -Wswitch-default -Wswitch-enum -Wstrict-aliasing=2 -Wfloat-equal
> -Wshadow -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o `test -f
> 'gui/main.cpp' || echo './'`gui/main.cpp
> gui/statusmenu.h: In function ‘GtkWidget*
> gm_mw_init_status_toolbar(GtkWidget*)’:
> gui/statusmenu.h:86: error: too few arguments to function ‘GtkWidget*
> status_menu_new(Ekiga::ServiceCore&)’
> gui/main.cpp:1708: error: at this point in file
> gui/main.cpp:1709: error: ‘struct _GmMainWindow’ has no member named ‘priv’
> gui/main.cpp:1709: error: ‘struct _GmMainWindow’ has no member named ‘priv’
> make[4]: *** [main.o] Error 1
> make[4]: Leaving directory `/home/dedu/softs/ekiga/ekiga/src'

Oups...

I can not test, but I think it is fixed.
--
_ Damien Sandras
(o-
//\ Ekiga Softphone : http://www.ekiga.org/
v_/_ Be IP : http://www.beip.be/
FOSDEM : http://www.fosdem.org/
SIP Phone : sip:dsandras@...

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Error compiling

2008-11-17T13:03:59Z

With stable branches, I have 2 compilation errors in ekiga:

g++ -DHAVE_CONFIG_H -I. -I..
-I../lib -I../lib/gmconf -I../lib/toolbox -I../lib/gui -I../lib/engine/
-I../lib/engine/gui/gtk-frontend -I../lib/engine/account/skel
-I../lib/engine/addressbook/skel -I../lib/engine/chat/skel
-I../lib/engine/presence/skel -I../lib/engine/protocol/skel
-I../lib/engine/protocol/sip -I../lib/engine/videooutput/skel
-I../lib/engine/videoinput/skel -I../lib/engine/audioinput/skel
-I../lib/engine/audiooutput/skel -I../lib/engine/hal/skel
-I../lib/engine/framework -I../lib/engine/gui/gtk-core -I../src
-I../src/clients/ -I../src/components/ -I../src/devices/
-I../src/endpoints/ -I../src/gui/ -I.. -DSCHEMA_AGE=62
-I../lib/engine/videooutput/common -I../lib/engine/videooutput/x
-D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12
-I/usr/include/pixman-1 -pthread -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -DORBIT2=1 -pthread -D_REENTRANT
-I/usr/include/libgnome-2.0 -I/usr/include/orbit-2.0
-I/usr/include/gconf/2 -I/usr/include/gnome-vfs-2.0
-I/usr/lib/gnome-vfs-2.0/include -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/include/libbonobo-2.0
-I/usr/include/bonobo-activation-2.0 -I/usr/include/libgnomeui-2.0
-I/usr/include/libart-2.0 -I/usr/include/gnome-keyring-1
-I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0
-I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/include/pango-1.0
-I/usr/include/gail-1.0 -I/usr/include/freetype2 -I/usr/include/atk-1.0
-I/usr/lib/gtk-2.0/include -I/usr/include/cairo -I/usr/include/directfb
-I/usr/include/libpng12 -I/usr/include/pixman-1
-I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DPTRACING=1
-D_REENTRANT -D_GNU_SOURCE=1 -fno-exceptions -I/usr/include/opal
-I/usr/include/SDL -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1
-fno-exceptions -I/usr/include/SDL -I/usr/include/sigc++-2.0
-I/usr/lib/sigc++-2.0/include -I/usr/include/libxml2 -D_REENTRANT
-I/usr/include/gtk-2.0 -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0
-I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0
-I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12
-I/usr/include/pixman-1 -Wall -g -O2 -Wall -Wextra -Winit-self
-Wswitch-default -Wswitch-enum -Wstrict-aliasing=2 -Wfloat-equal
-Wshadow -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o `test -f
'gui/main.cpp' || echo './'`gui/main.cpp
gui/statusmenu.h: In function ‘GtkWidget*
gm_mw_init_status_toolbar(GtkWidget*)’:
gui/statusmenu.h:86: error: too few arguments to function ‘GtkWidget*
status_menu_new(Ekiga::ServiceCore&)’
gui/main.cpp:1708: error: at this point in file
gui/main.cpp:1709: error: ‘struct _GmMainWindow’ has no member named ‘priv’
gui/main.cpp:1709: error: ‘struct _GmMainWindow’ has no member named ‘priv’
make[4]: *** [main.o] Error 1
make[4]: Leaving directory `/home/dedu/softs/ekiga/ekiga/src'

--
Eugen
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: I need brains!

2008-11-17T12:47:48Z

Julien Puydt a écrit :
> sigc::bind_functor<0,
> sigc::bound_const_mem_functor2<void, sigc::signal2<void,
> gmref_ptr<Ekiga::Book>, gmref_ptr<Ekiga::Contact>, sigc::nil>,
> gmref_ptr<Ekiga::Book> const&, gmref_ptr<Ekiga::Contact> const&>,
> gmref_ptr<Evolution::Book>, sigc::nil, sigc::nil, sigc::nil, sigc::nil,
> sigc::nil, sigc::nil> >

I banged my head to the wall a few times and decided that was coming
from those three lines in source-impl.h's template<typename BookType>
void Ekiga::SourceImpl<BookType>::add_book (gmref_ptr<BookType> book)
method :

add_connection (book, book->contact_added.connect (sigc::bind<0>
(contact_added.make_slot (), book)));

add_connection (book, book->contact_removed.connect (sigc::bind<0>
(contact_removed.make_slot (), book)));

add_connection (book, book->contact_updated.connect (sigc::bind<0>
(contact_updated.make_slot (), book)));

because everytime we do a sigc:bind0 from a some_signal.make_slot()
where some_signal is sigc::signal<void, gmref_ptr<Book>,
gmref_ptr<Contact> >...

I'm still investigating, but it's getting hot.

Snark
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: I need brains!

2008-11-17T12:28:14Z

Eugen Dedu a écrit :

> Julien Puydt wrote:
>> Damien Sandras a écrit :
>>> Multithreading ?
>>>
>>> Perhaps you could check the thread name. What would be nice to do, is
>>> being able to monitor the ref count value in real time for that object.
>>
>> The lines of code which give that are next to each other : they can't
>> be from different threads. And what you see *is* monitoring the count
>> value in real time. :-(
>
> Two threads CAN execute the same code, so it should be interesting to
> print also the thread id. However, I don't know how ekiga works...

Two threads in the GUI would be a very terrible bug.

No, it's definitely not a threading issue :-(

Snark
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: I need brains!

2008-11-17T11:33:32Z

Julien Puydt wrote:
> Damien Sandras a écrit :
>> Multithreading ?
>>
>> Perhaps you could check the thread name. What would be nice to do, is
>> being able to monitor the ref count value in real time for that object.
>
> The lines of code which give that are next to each other : they can't be
> from different threads. And what you see *is* monitoring the count value
> in real time. :-(

Two threads CAN execute the same code, so it should be interesting to
print also the thread id. However, I don't know how ekiga works...

--
Eugen
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: I need brains!

2008-11-17T11:30:26Z

Julien Puydt a écrit :
> the crash-on-exit bug which cripples ekiga since too long.

> I have no clue why. Help!

If :
- I compile out evolution-data-server ;
- I disconnect forcefully the GUI from the engine in the
roster&addressbook windows (which makes ekiga unusable...) ;
- I put back the memory management (make gmref.cpp call delete again) ;

then I don't get crashes.

This makes me wonder if there aren't *two* crashers, helping each other
escape a proper fix.

Here is the backtrace from the evolution crash :
#0 0x00000500 in ?? ()
#1 0xb7002dbb in sigc::trackable::notify_callbacks() ()
from /usr/lib/libsigc-2.0.so.0
#2 0xb7002e2d in sigc::trackable::~trackable() ()
from /usr/lib/libsigc-2.0.so.0
#3 0xb700287a in sigc::signal_base::~signal_base() ()
from /usr/lib/libsigc-2.0.so.0
#4 0x0817d11f in ~Book (this=0x832ee00, __vtt_parm=0x824ec58)
at /usr/include/sigc++-2.0/sigc++/signal.h:1663
#5 0x081ec5a3 in ~BookImpl (this=0x832ee00, __vtt_parm=0x824ec54)
at ../../../../lib/engine/addressbook/skel/book-impl.h:157
#6 0x081e93e1 in ~Book (this=0x832ee00)
at ../../../../lib/engine/addressbook/evolution/evolution-book.cpp:220
#7 0x080f8b88 in gmref_dec (obj=0xb673e160) at gmref.cpp:60
#8 0x081c5f41 in ~gmref_ptr (this=0x832fe98)
at ../../../../lib/gmref/gmref.h:207
#9 0x081c63f2 in sigc::internal::typed_slot_rep<sigc::bind_functor<0,
sigc::bound_const_mem_functor2<void, sigc::signal2<void,
gmref_ptr<Ekiga::Book>, gmref_ptr<Ekiga::Contact>, sigc::nil>,
gmref_ptr<Ekiga::Book> const&, gmref_ptr<Ekiga::Contact> const&>,
gmref_ptr<Evolution::Book>, sigc::nil, sigc::nil, sigc::nil, sigc::nil,
sigc::nil, sigc::nil> >::destroy (data=0x832fe68)
at /usr/include/sigc++-2.0/sigc++/adaptors/bound_argument.h:51
#10 0xb700335d in sigc::internal::slot_rep::notify(void*) ()
from /usr/lib/libsigc-2.0.so.0
#11 0xb7002d5a in
sigc::internal::trackable_callback_list::~trackable_callback_list() ()
from /usr/lib/libsigc-2.0.so.0
#12 0xb7002dbb in sigc::trackable::notify_callbacks() ()
from /usr/lib/libsigc-2.0.so.0
#13 0xb7002e2d in sigc::trackable::~trackable() ()
from /usr/lib/libsigc-2.0.so.0
#14 0xb700287a in sigc::signal_base::~signal_base() ()
from /usr/lib/libsigc-2.0.so.0
#15 0x081c8fd8 in Ekiga::SourceImpl<Evolution::Book>::~SourceImpl() ()
#16 0x081c59ad in ~Source (this=0x82c3b58)
at
../../../../lib/engine/addressbook/evolution/evolution-source.cpp:160
#17 0x080f8b88 in gmref_dec (obj=0xb673e160) at gmref.cpp:60
#18 0x080d6ff1 in ~gmref_ptr (this=0x83301e0) at ../lib/gmref/gmref.h:207
#19 0x08129d11 in ~ServiceCore (this=0x828bb78)
at /usr/include/c++/4.3/ext/new_allocator.h:118
#20 0x080f6c18 in GnomeMeeting::Exit (this=0x8253760) at ekiga.cpp:119
#21 0x080e3801 in main (argc=0, argv=0x8618274, envp=Cannot access
memory at address 0x20
) at gui/main.cpp:4557

What does that mean? Well, at shutdown, we free the Ekiga::ServiceCore,
which frees the Evolution::Source, which frees a signal, which frees a
gmref_ptr (which was there because a sigc::bind was connected to the
signal), which frees an Evolution::Book, which frees a signal... and
there it crashes, and I don't know exactly why (!).

What I find quite startling is that the LDAP code and the call-history
code, which are organized like the EDS code... doesn't crash! So the
problem has to be something pretty unique to the EDS code...

Before you ask : that evolution crash does go away if I comment out the
memory freeing in gmref.cpp... so it may share a common root with the
crash in the GUI code.

Help, I need somebody! Help, not just anybody! Help, you know I need
someone, help!

Snark
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: I need brains!

2008-11-16T00:28:33Z

Hi,

here is the source of a backtrace dumper to follow each and every
gmref_inc/gmref_dec in ekiga (and can print "THIS:" for objects of
interest though that is commented out).

It uses nemiver-as-a-lib (needs svn from nemiver and snapshot from gdb,
and the target program can't print anything on console -- gdb bug).

Snark

#include <iostream>
#include <glibmm.h>

#include <common/nmv-initializer.h>
#include <common/nmv-safe-ptr-utils.h>
#include <dynmods/nmv-i-debugger.h>

using namespace nemiver;
using namespace nemiver::common;

Glib::RefPtr<Glib::MainLoop> loop = Glib::MainLoop::create(Glib::MainContext::get_default ());

static void
on_signal_received_signal (const UString& msg,
const UString& cookie)
{
std::cerr << "SIGNAL: " << msg << std::endl;
}

static void
on_error_signal (const UString& message,
IDebuggerSafePtr& debugger)
{
debugger->do_continue ();
}

static void
on_variable_value_signal (const UString& name,
const IDebugger::VariableSafePtr& variable,
const UString& cookie,
IDebuggerSafePtr& debugger)
{
if (name == "this") {

std::cerr << "THIS: " << variable->value () << std::endl;
debugger->do_continue ();
} else if (name == "obj") {

debugger->list_frames (variable->value ());
} else {

debugger->do_continue ();
}
}

static void
on_frames_listed_signal (const vector<IDebugger::Frame> frames,
const UString& obj,
IDebuggerSafePtr& debugger)
{
std::cout << "Backtrace:" << std::endl;
vector<IDebugger::Frame>::const_iterator iter = frames.begin ();
std::cout << "\t" << iter->function_name () << " " << obj << std::endl;
++iter;
for ( /* nothing */ ;
iter != frames.end ();
++iter)
std::cout << "\t" << iter->function_name () << std::endl;
std::cout.flush ();
debugger->do_continue ();
}

static void
on_stopped_signal (IDebugger::StopReason a_reason,
bool has_frame,
const IDebugger::Frame& frame,
int thread_id,
int breakpoint_number,
const UString& cookie,
IDebuggerSafePtr& debugger)
{
switch (a_reason) {

case IDebugger::BREAKPOINT_HIT:

if (has_frame) {

if (frame.function_name () == "gmref_inc"
|| frame.function_name () == "gmref_dec") {

debugger->print_variable_value ("obj");
} else
debugger->print_variable_value ("this");
}
break;

default:
loop->quit ();
}
}

int
main (int argc,
char* argv[])
{

NEMIVER_TRY

Initializer::do_init ();

DynamicModuleManager module_manager ;
IDebuggerSafePtr debugger = module_manager.load_iface<IDebugger> ("gdbengine", "IDebugger");

debugger->set_event_loop_context (loop->get_context ());
std::vector<UString> args;
std::vector<UString> source_search_dir;

source_search_dir.push_back (".");
args.push_back (argv[1]);

debugger->error_signal ().connect (sigc::bind (&on_error_signal, debugger));

debugger->stopped_signal ().connect (sigc::bind (&on_stopped_signal,
debugger));

debugger->frames_listed_signal ().connect (sigc::bind (&on_frames_listed_signal, debugger));

debugger->variable_value_signal ().connect (sigc::bind (&on_variable_value_signal, debugger));

debugger->signal_received_signal ().connect (&on_signal_received_signal);

debugger->load_program (args, "", source_search_dir);

//debugger->set_breakpoint ("avahi-heap.cpp", 91);
//debugger->set_breakpoint ("local-heap.cpp", 52);
debugger->set_breakpoint ("gmref_inc");
debugger->set_breakpoint ("gmref_dec");

debugger->run ();
loop->run ();

NEMIVER_CATCH_AND_RETURN_NOX (-1)

return 0;
}

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: I need brains!

2008-11-15T08:04:02Z

Damien Sandras a écrit :
> Multithreading ?
>
> Perhaps you could check the thread name. What would be nice to do, is
> being able to monitor the ref count value in real time for that object.

The lines of code which give that are next to each other : they can't be
from different threads. And what you see *is* monitoring the count value
in real time. :-(

That kills me :-(

Snark
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: I need brains!

2008-11-15T07:25:47Z

Le samedi 15 novembre 2008 à 16:12 +0100, Julien Puydt a écrit :

> Hi,
>
> I committed log-printing code in ekiga -- and I need help to make sense
> of it. This is very directly related to the crash-on-exit bug which
> cripples ekiga since too long.
>
> The problem is found in that piece of log :
>
> void on_heap_updated(gmref_ptr<Ekiga::Cluster>, gmref_ptr<Ekiga::Heap>,
> void*), 0xb5602144 -> 11
> GmRefCounted* gmrefcounted_boxed_copy(GmRefCounted*), 0xb5602144 -> 1
>
> Here you see a same object (0xb5602144) which has a refcount of 11 for
> the engine and 1 for gtk+.
>
> I have no clue why. Help!

Multithreading ?

Perhaps you could check the thread name. What would be nice to do, is
being able to monitor the ref count value in real time for that object.
--
_ Damien Sandras
(o-
//\ Ekiga Softphone : http://www.ekiga.org/
v_/_ Be IP : http://www.beip.be/
FOSDEM : http://www.fosdem.org/
SIP Phone : sip:dsandras@...

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

I need brains!

2008-11-15T07:12:06Z

Hi,

I committed log-printing code in ekiga -- and I need help to make sense
of it. This is very directly related to the crash-on-exit bug which
cripples ekiga since too long.

The problem is found in that piece of log :

void on_heap_updated(gmref_ptr<Ekiga::Cluster>, gmref_ptr<Ekiga::Heap>,
void*), 0xb5602144 -> 11
GmRefCounted* gmrefcounted_boxed_copy(GmRefCounted*), 0xb5602144 -> 1

Here you see a same object (0xb5602144) which has a refcount of 11 for
the engine and 1 for gtk+.

I have no clue why. Help!

Snark
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

ekiga entered debian repository

2008-11-14T14:24:09Z

Hello,

We have the pleasure to inform you that ekiga 3.0.1 has just been
uploaded in debian experimental distribution, cf.
http://packages.qa.debian.org/e/ekiga.html. It might take a few days to
be available on all architectures.

Happy ekiga,
--
Eugen
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: Testing of bug 558587

2008-11-13T15:51:32Z

On Thu, Nov 13, 2008 at 11:45 PM, Martin Ebourne <lists@...> wrote:
> On Thu, 2008-11-13 at 23:16 +0000, Peter Robinson wrote:
>> > Just building a test at the moment. I should be able to test it shortly.
>>
>> Initial tests look good to me :-D
>
> This looks like the bug responsible for the patch:
> https://bugzilla.redhat.com/show_bug.cgi?id=459119

Yes, it also looks like the breakage has been reverted/fixed upstream
in a later commit I've filed a bug to have the patch reverted but
either way we have a fix for ekiga for Fedora 10 Final that works
which ever way.

Cheers,
Peter
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: Testing of bug 558587

2008-11-13T15:45:56Z

On Thu, 2008-11-13 at 23:16 +0000, Peter Robinson wrote:
> > Just building a test at the moment. I should be able to test it shortly.
>
> Initial tests look good to me :-D

This looks like the bug responsible for the patch:
https://bugzilla.redhat.com/show_bug.cgi?id=459119

Cheers,
Martin

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: Testing of bug 558587

2008-11-13T15:16:43Z

>>> Same, with a couple of patches from upstream. The one that looks like
>>> it might be an issue has the change log entry "Handled extra parameter
>>> of closed signal
>>> " Patch can be seen here
>>> http://cvs.fedoraproject.org/viewvc/rpms/libnotify/F-10/libnotify-closed-reason.patch?view=markup
>>
>> That explains it.
>>
>> Changing the API without changing the version number and breaking
>> compatibility is not a very wise thing to do.
>>
>> Try changing :
>> static void
>> closed_cb (NotifyNotification * /*notify*/,
>> gpointer main_window)
>> in main.cpp into
>> static void
>> closed_cb (NotifyNotification * /*notify*/,
>> gint /*reason*/,
>> gpointer main_window)
>>
>> It should work.
>
> Just building a test at the moment. I should be able to test it shortly.

Initial tests look good to me :-D

Cheers,
Peter
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list