On Fri, Feb 15, 2008 at 04:14:46PM -0500, Ted Guild wrote:
> I'm running Debian Testing (Lenny) AMD64 release. Barry 0.11 and
> Opensync 0.22 lib, msynctool and plugins built from source with CFLAGS
> -g.
>
> It segfaults when I try to do a sync with msynctools. Although I
> would appreciate any pointers with opensync if there is a way to
> upload LDIF address books with btool or perhaps edit the address book
> in the tarball backup I'd be interested to know how.
There is an "upldif" command line tool available with Barry that will
*replace* your address book with the contents of LDIF. Note the word
replace. Any existing addresses in your Blackberry will be erased, but
if you're restoring an empty device, this may be what you want.
Examples:
ldapsearch -x | upldif
This dumps a log of what upldif can parse. If it looks good, and what you
want your blackberry to look like, do:
ldapsearch -x | upldif -u
You may need to filter the ldapsearch output a little more, depending on your
LDAP database.
> msynctool --sync kde2phone
> gdb /usr/local/bin/msynctool core.28417
> Program terminated with signal 11, Segmentation fault.
> #0 0x00002b18dfc53000 in strlen () from /lib/libc.so.6
Since you built with -g, all you should need is a core dump file.
ulimit -c unlimited
<make it crash>
gdb /path/to/msynctool /path/to/corefile
This will likely give you a message stating that the core file does not
match, and which binary actually crashed. This is often "osplugin" from
opensync, which turns out to be:
gdb /usr/lib/opensync/osplugin /path/to/corefile
Once it loads successfully, use the "bt" backtrace command and send
me the output.
Thanks,
- Chris
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Barry-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/barry-devel
