I'm really unsure if this is the desired output as I am totally
unfamiliar with debugging,
(gdb) bt
#0 0x2b85bdd27a70 in ?? () from /lib64/ld-linux-x86-64.so.2
#1 0x2b85bf9088d9 in ?? ()
#2 0x00657000 in ?? ()
#3 0x00642a90 in ?? ()
#4 0x in ?? ()
On Fri, Nov 02, 2007 at 01:50:37PM -0700, Yigal Weinstein wrote:
I'm really unsure if this is the desired output as I am totally
unfamiliar with debugging,
(gdb) bt
#0 0x2b85bdd27a70 in ?? () from /lib64/ld-linux-x86-64.so.2
#1 0x2b85bf9088d9 in ?? ()
#2 0x00657000 in ??
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
On Mon, Oct 29, 2007 at 10:43:49AM +, Javier Arregui wrote:
As you can see, the DTSTART from the VTIMEZONE part is retrieved from
barry before the DTSTART VEVENT one. How can I avoid that? If you
know a quick patch, probably in vformat.c..
This has just been fixed in CVS thanks to
