[Ekiga-devel-list] ekiga on thin clients
Hi All, Just discovered that this company ship ekiga as a voip client on their thin clients for those that are interested. http://www.igel.com/ Peter ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] windows stable branch
Michael Rickmann wrote: Am Freitag, den 08.05.2009, 17:40 +0200 schrieb Eugen Dedu: Michael Rickmann wrote: Am Freitag, den 08.05.2009, 13:41 +0200 schrieb Eugen Dedu: Hi, Windows build is currently delayed by a few bugs. Couldn't we just create a windows build from the stable branch? Are there modifications to be done or is it as simple as just build the branch instead of the trunk? I can try during weekend. What is the stable branch - the tar ball ekiga 3.2 ? My patches to build ekiga master with device detection you find in http://mail.gnome.org/archives/ekiga-devel-list/2009-May/msg3.html Should the above patch be applied right now? Or do you wait for another solution? http://sourceforge.net/tracker/?func=detailaid=2785005group_id=204472atid=989748 -- Eugen ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Crash on exit : dead?
Eugen Dedu a écrit : Julien Puydt wrote: I had once again checked the memory management in both the contact and presence stacks, without finding any problem. I read the valgrind errors again and decided they meant a problem with sigc::trackable : I changed to manual tracking, and got a big improvement of the valgrind log. Does that fix the crash on exit? Very glad to discover that, even after four executions, I have no crash anymore!! W O N D E R F U L ! ! ! I still have no clue why sigc::trackable gave those problems though... Don't forget to fix it in the branch too. Ah, yes ; I'll have to. However, valgrind still shows many errors of the following type: ==24513== Mismatched free() / delete / delete [] in ptlib or ekiga. I attach the output. Looking at it, the worse offender is PAbstractArray -- but perhaps it's a false positive? There is also a problem with the regular expression compilation... again in ptlib. You should probably report upstream. Last hurdle for 3.2.1 : the call history is broken. Snark ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
