opensync-users

[Opensync-users] Problem running tests for trunk

[Tyson W. <twh...@gm...>]

Hi,

I've not been able to sync my Nokia 2760 using the Debian opensync packages, 
so I've compiled up the trunk version (as of right now) of both wbxml2 and 
libsyncml to see if the issues have been resolved.

Unfortunately, libsyncml seems to be hanging on the session_transmit test.  
Turning on the trace shows you first get _event_callback with 1, then with 5, 
then it dispatches 2 status, and then it goes into a endless loop of

 smlSessionReceiveBody: command 1 of message 1 found
 smlSessionReceiveBody: Now dispatching 1 statuses. Sessionwaiting: 0, prio: 1
 >>>>>>>  smlSessionDispatch
         smlSessionDispatch: dispatch status - 1
         >>>>>>>  _smlSessionCommandHandler
                 _smlSessionCommandHandler: session cmd type 2
         <<<<<<<  _smlSessionCommandHandler - next needed command status 0 for 
message 1 is not this one (cmd 1, msg 1)
 <<<<<<<  smlSessionDispatch - done

 (I would be happy to send all the earlier stuff the lead up if it is useful)

Thanks!

-Tyson

Re: [Opensync-users] Problem running tests for trunk

[Michael B. <mic...@cm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Tyson,

which version do you use?

Tyson Whitehead wrote:
> 
> I've not been able to sync my Nokia 2760 using the Debian opensync packages, 
> so I've compiled up the trunk version (as of right now) of both wbxml2 and 
> libsyncml to see if the issues have been resolved.
> 
> Unfortunately, libsyncml seems to be hanging on the session_transmit test.  
> Turning on the trace shows you first get _event_callback with 1, then with 5, 
> then it dispatches 2 status, and then it goes into a endless loop of
> 
>  smlSessionReceiveBody: command 1 of message 1 found
>  smlSessionReceiveBody: Now dispatching 1 statuses. Sessionwaiting: 0, prio: 1
>  >>>>>>>  smlSessionDispatch
>          smlSessionDispatch: dispatch status - 1
>          >>>>>>>  _smlSessionCommandHandler
>                  _smlSessionCommandHandler: session cmd type 2
>          <<<<<<<  _smlSessionCommandHandler - next needed command status 0 for 
> message 1 is not this one (cmd 1, msg 1)
>  <<<<<<<  smlSessionDispatch - done

This means that one SyncML status is not handled. Which platform do you
use? I only test with x86 multi core. I release only if our build hosts
are clean but we have not all platform configurations of course.

Best regards

Michael
- --
___________________________________________________________________

Michael Bell                        Humboldt-Universitaet zu Berlin

Tel.: +49 (0)30-2093 2482           ZE Computer- und Medienservice
Fax:  +49 (0)30-2093 2704           Unter den Linden 6
mic...@cm...       D-10099 Berlin
___________________________________________________________________

PGP Fingerprint: 09E4 3D29 4156 2774 0F2C  C643 D8BD 1918 2030 5AAB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkp/3QQACgkQ2L0ZGCAwWqs0gwCgwpt2pwW8WUdI+R/V2NtS8BnD
rpkAoKEiQM7gGnQn7BJQN1kjE5P5w4/l
=ViRU
-----END PGP SIGNATURE-----