Re: [coldsync-hackers] Tungsten-W sync problems...

[Izzy Blacklock <izzyb at ecn dot ab.ca>]

On Monday 03 November 2003 06:01 pm, Alessandro Zummo wrote:

> > I found that removing -d sync:6 stops the segfault and produces the
> > second file in the attachment.  Here's the command and screen output:
>
>  interesting. can you use gdb to see where the segfault is happening?
>

Ok, I was able to figure out how to get gdb working.  In not fully sure what 
it is I'm doing, but I'm hoping this output will be useful to you.  Let me 
know if you want me to do anything else. 

(gdb) run -d sync:6 -p /dev/usb/tts/0 -mb testsync
Starting program: /usr/local/bin/coldsync -d sync:6 -p /dev/usb/tts/0 -mb 
testsync
Summary of sync configuration:
Listen:

Program received signal SIGSEGV, Segmentation fault.
0x4018985b in strlen () from /lib/i686/libc.so.6
(gdb) bt
#0  0x4018985b in strlen () from /lib/i686/libc.so.6
#1  0x4015b55b in vfprintf () from /lib/i686/libc.so.6
#2  0x4015c32e in vfprintf () from /lib/i686/libc.so.6
#3  0x401580c1 in vfprintf () from /lib/i686/libc.so.6
#4  0x4016130f in fprintf () from /lib/i686/libc.so.6
#5  0x0804d712 in load_config (read_user_config=True) at config.c:609
#6  0x0804a464 in main (argc=1, argv=0xbffff71c) at coldsync.c:237
#7  0x40126c57 in __libc_start_main () from /lib/i686/libc.so.6

Looks like it was libc.so.6 function strlen() that segfaulted?  I'm not sure 
how to proceed from here?  This is a mandrake 9.2 system, if that helps any, 
and I'm still using the coldsync-3.0-pre3.tar.gz.  Perhaps this has already 
been fixed in the CVS?  See my other note re compiling problems with the CVS.

...Izzy

This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.