Re: [Ekiga-list] Status of Win port

[Eugen Dedu <Eugen Dedu pu-pm univ-fcomte fr>]

Michael Rickmann wrote:
> Hello everybody,
>
> Am Dienstag, den 07.04.2009, 11:05 -0500 schrieb Michael Cronenworth:
> > -------- Original Message --------
> > Subject: Re: [Ekiga-list] Status of Win port
> > From: Eugen Dedu <Eugen Dedu pu-pm univ-fcomte fr>
> > To: Ekiga mailing list <ekiga-list gnome org>
> > Date: 04/07/2009 10:09 AM
> >
> > > So the compilation works, with all classical options.
> > Yes, it compiles, but you cannot use it. (register/crash bug) I can 
> > provide you the installer if you would like.
> I can can confirm successful compilation and bugs. You can find my
> Makefile and patches in
> http://wwwuser.gwdg.de/~mrickma/ekiga/ekiga_build.tgz 

ptlib_configure.ac* are identical, isn't it?

Could you retest with current svn please and tell us if if the other 
patches are necessary (so that they be integrated in svn)?  (thanks for 
the other patches anyway!)

> > > Fails to register: Could you send us a -d 4 output?  (I haven't seen 
> > > any, sorry)
> My mail  with d4 output was bounced, too long. The d4 was produced by
> starting ekiga on WinXP which was configured for my account at ekiga.net
> and thereafter shutting it down (crash). When comparing it to other d4
> outputs (v3.2 Ubuntu Intrepid, v3.0.2 WinXP, v3.2 Linux Wine, see
> http://wwwuser.gwdg.de/~mrickma/ekiga/logs-040709.tar.gz ) the Windows
> v3.2 outputs lack any reference to the stun server and contain a
> conspicous line
> Contact: <sip:mrickma 192 168 1 18>;q=1 .
> That is my IP behind a NAT router.

If I understand correctly, win version does not use stun, is that right? 
 If this is the case, is the stun checkbox in preferences used?

> > I may have mistaken it for the crash on exit bug. I'll compile a output 
> > dump this evening, but 3.0.2 still works fine on the same box.
> >
> > > Crash on exit: The only remaining bug (to my knowledge) is 
> > > http://bugzilla.gnome.org/show_bug.cgi?id=577640.

Let's stop speaking about crash on exit, it is known and will eventually 
be fixed.

> When I look at the logs the v3.2 WinXP gives up first (after PWLib
> Destroyed thread 0x9655cbc VideoPreviewManager) at a point from which
> the well behaving v3.2 Ubuntu Intrepid version continues with "Deadlock
> potential - avoiding evil bug!" apparently from liborbit2 (Google says
> so, no idea).

No idea either...

--
Eugen