Re: [Opensync-users] libsyncml failure with N97

[Bernhard R. <ber...@in...>]

On Monday 02 November 2009, Michael Bell wrote:
> > From source I've build, on a big endian powerpc GNU/Debian Lenny system:
> > build:

> > libwbxml-0.10.7
> > libsyncml-0.5.4

> > b) Side problem:
> > Exporting SYNCML_TRACE=/tmp/somedir
> > lead to a seqmentation fault. (SYNCML_LOG was also set and worked).
>
> Do you still have the logged messages?

bin/syncml-ds-tool -u 0 --identifier "PC Suite" --wbxml --sync text/x-vcard 
Contacts
worked for me today, I have no idea why it works today, this is the same 
command as I was trying a few days ago.

> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 0x490304d0 (LWP 15122)]
> > 0x0fa644c8 in strlen () from /lib/libc.so.6
> > (gdb) bt
> > #0  0x0fa644c8 in strlen () from /lib/libc.so.6
> > #1  0x0fa2d364 in vfprintf@@GLIBC_2.4 () from /lib/libc.so.6
> > #2  0x0fa528e8 in vasprintf@@GLIBC_2.4 () from /lib/libc.so.6
> > #3  0x0fee27c8 in g_vasprintf () from /usr/lib/libglib-2.0.so.0
> > #4  0x0fec8798 in g_strdup_vprintf () from /usr/lib/libglib-2.0.so.0
> > #5  0x0ff87c74 in smlTrace ()
> >    from /mobilehome/bernhard/hacking/opensync/lib/libsyncml.so.2
> > #6  0x0ff8a33c in smlTransportReceiveEvent ()
> >    from /mobilehome/bernhard/hacking/opensync/lib/libsyncml.so.2
>
> This is a bug in a trace statement. Do you have the generated traces
> before the crash happens? Usually this is a good description of the
> error condition.

Attached as 20091111-crash.tar.bz2, HTH.


-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Deputy Germany Coordinator: fsfeurope.org. Coordinator: Kolab-Konsortium.com.
Intevation GmbH, Neuer Graben 17, Osnabrück, DE; AG Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner