On Tue, Oct 30, 2007 at 03:08:49AM -0700, Yigal Weinstein wrote: > Chris, > > This is the consistent output: > > $breset > $msynctool --sync evo2-sync > Synchronizing group "evo2-sync" > The previous synchronization was unclean. Slow-syncing > Member 1 of type evo2-sync just connected > Member 2 of type barry-sync just connected > All clients connected or error > Segmentation fault > Pipe closed! Exiting.
Could you run the following: ulimit -c unlimited # turn on core dumps msynctool --sync evo2-sync (search for core file) gdb /usr/bin/msynctool corefile (this will make gdb tell you which file caused the core dump... exit gdb and run it again with the given file) gdb /path/to/file/gdb/gave corefile Then use the "bt" command, and send me the output. Thanks! - Chris ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Barry-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/barry-devel
