From: Mariano R. <ml...@da...> - 2006-03-11 12:53:03
|
On Sat, 2006-03-11 at 12:46 +0100, Armin Bauer wrote: > > Hi, > > it probably a undiscovered bug regarding 64 bit platforms. Can you > please send me a gdb trace of the crash? > > Best Regards, > Armin Bauer > Hello, Armin: I'm sending this to you and the list, since I'm not sure you meant "send me" literally ;) Is this what you need? I'm sorry if not (I haven't used gdb before). Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 46912498464928 (LWP 28003)] 0x00002aaaaabd1718 in osync_member_initialize (member=0x0, error=0x7fffff86b788) at opensync_member.c:982 982 if (!(member->plugindata = functions.initialize(member, error))) { This happened when run: (gdb --args) msynctool --sync prueba2 where prueba2 is: Groupname: prueba2 Member 1: evo2-sync Configuration : <?xml version="1.0"?> <config><adress_path>default</adress_path><calendar_path>default</calendar_path><tasks_path>default</tasks_path></config> Member 2: evo2-sync Configuration : <?xml version="1.0"?> <config><adress_path>default</adress_path><calendar_path>default</calendar_path><tasks_path>default</tasks_path></config> Do you want me to gdb it with other pairs? Let's say file-sync/evo2? Also, could you tell me where's synce plugin? Thank you very much, Mariano López Reta |