Menu
▾
▴
Re: [Opensync-users] Unknown CTCapType for Property: ParamName
|
From: Michael B. <mic...@cm...> - 2009-08-10 09:32:11
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Tyson, Tyson Whitehead wrote: > > I decided to give the trunk syncml-ds-tool and wbxml a try despite the > session_transmit test failing. I get the same problems I get with the lastest > Debian packages (which are version 0.5.3 of libsyncml and 0.10.6 of wbxml). > > $ syncml-ds-tool -b xx:xx:xx:xx:xx:xx yy --wbxml --identifier "PC Suite" -- > sync text/x-vcard Contacts > ** Message: Remote device was successfully connected. > ** Message: ERROR: Unknown CTCapType for Property: ParamName This looks like a bug. ParamName is not a property and usually the Nokias work because I test with them. I will test it with my mobiles. BTW has your Nokia a S60 or S40 OS? > and if I enable tracing and logging it segment faults > > $ syncml-ds-tool -b xx:xx:xx:xx:xx:xx yy --wbxml --identifier "PC Suite" -- > sync text/x-vcard Contacts > Segmentation fault This looks like a bug in trace statement after an interface change. trunk: r1251 branches/libsyncml-0.5.x: r1255 > Compiling with debugging information and running under gdb with or without > tracing and logging enabled I get the message > > ** ERROR **: A disconnect event was received but there is no connected > transport. > aborting... Clearly a bug. Perhaps a race condition. Do you have the traces from this error? I committed a patch to trunk. trunk: r1252, r1253 and r1254 branches/libsyncml-0.5.x: r1256 > and backtracing for the third thread above shows > > #0 0x00007f2b7529d065 in raise () from /lib/libc.so.6 > #1 0x00007f2b752a0153 in abort () from /lib/libc.so.6 > #2 0x00007f2b76ccf0de in IA__g_logv (log_domain=0x0, > log_level=G_LOG_LEVEL_ERROR, format=0x7f2b76fbb660 "A disconnect event was > received but there is no connected transport.", args1=0x7f2b72fa9c40) at > /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmessages.c:506 > #3 0x00007f2b76ccf163 in IA__g_log (log_domain=0x1a97 <Address 0x1a97 out of > bounds>, log_level=6809, format=0x6 <Address 0x6 out of bounds>) at > /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmessages.c:526 > #4 0x00007f2b76f7b897 in smlTransportReceiveEvent (tsp=0x1a92ff0, link_=0x0, > type=SML_TRANSPORT_EVENT_DISCONNECT_DONE, data=0x0, error=0x0) at > /home/tyson/Sync/libsyncml/libsyncml/sml_transport.c:303 > #5 0x00007f2b76fad587 in smlTransportObexClientEvent (handle=0x1a932a0, > object=0x1aa0930, mode=<value optimized out>, event=4, obex_cmd=2, obex_rsp=0) > at /home/tyson/Sync/libsyncml/libsyncml/transports/obex_client.c:570 > #6 0x00007f2b755c1463 in ?? () from /usr/lib/libopenobex.so.1 > #7 0x00007f2b755c0fb7 in ?? () from /usr/lib/libopenobex.so.1 > #8 0x00007f2b76fab21f in smlTransportObexClientSend (userdata=0x1a930b0, This looks like an error during the first message. > Running the debug version from the command line or under valgrind gives the > earlier results (i.e., "ERROR: Unknown CTCapType for Property: ParamName"). > Valgrind also complains about 8 "conditional jumps or moves depending on > uninitializsed values" within ld-2.9.so, but I assume that is irrelevant. I try to simulate this with my mobiles too. Let's see. > * 1 process 6959 0x00007f8f74b2fcc0 in strlen () from /lib/libc.so.6 > > and a backtrace on the first thread gives > > #0 0x00007f8f74b2fcc0 in strlen () from /lib/libc.so.6 > #1 0x00007f8f74afc9ae in vfprintf () from /lib/libc.so.6 > #2 0x00007f8f74b1d43f in vasprintf () from /lib/libc.so.6 > #3 0x00007f8f76544ec0 in IA__g_vasprintf (string=0x3, > format=0x7f8f76806ba6 "%s: connect + no link", args=0x7f8f72844a70) > at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gprintf.c:315 > #4 0x00007f8f76531b00 in IA__g_strdup_vprintf (format=0x3 <Address 0x3 out of > bounds>, > args=<value optimized out>) > at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gstrfuncs.c:244 > #5 0x00007f8f767c3b9d in smlTrace (type=TRACE_INTERNAL, > message=0x7f8f76806ba6 "%s: connect + no link") Some wrong trace statements. Fixed in trunk and branches/libsyncml-0.5.x > I would be happy to provide any additional information I can or test any > patches that anyone proposes. Well, you already provied more informations than the most other users in the first message. Thanks a lot. The most important question is which mobile OS do you use? I have both but it reduces my workload if I now what I have to test ;) Thanks for the detailed description 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/6T0ACgkQ2L0ZGCAwWqvOOACdFhH/t6v7GMzr+g9cak7IBfQW xTsAoNZKF7MunYWE8ZSjGnwcROhcc9nG =dhAC -----END PGP SIGNATURE----- |
