|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
|
|
segfault on synci am in debian testing:
please if need another specific info, tell me. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb24ceb90 (LWP 14051)] 0xb7ddd263 in strchr () from /lib/i686/cmov/libc.so.6 (gdb) bt #0 0xb7ddd263 in strchr () from /lib/i686/cmov/libc.so.6 #1 0xb7ef82f5 in osync_time_isutc (vtime=0x0) at /build/mbanck/opensync-0.22/opensync/opensync_time.c:154 #2 0xb7fd3aec in osxml_compare_time (leftnode=0xb12f6990, rightnode=0xb12efff8) at /build/mbanck/opensync-0.22/formats/vformats-xml/xml- support.c:62 #3 0xb7fd3fdf in osxml_compare_node (leftnode=0xb12f6990, rightnode=0xb12efff8) at /build/mbanck/opensync-0.22/formats/vformats-xml/xml- support.c:177 #4 0xb7fd3f58 in osxml_compare_node (leftnode=0xb12efdb0, rightnode=0xb12f6748) at /build/mbanck/opensync-0.22/formats/vformats-xml/xml- support.c:182 #5 0xb7fd43ee in osxml_compare (leftinpdoc=0xb11e37a0, rightinpdoc=0xb1209ec0, scores=0xb24ce124, default_score=0, treshold=99) at /build/mbanck/opensync-0.22/formats/vformats-xml/xml-support.c:335 #6 0xb5575250 in compare_vevent (leftchange=0x83a9408, rightchange=0x8389568) at /build/mbanck/opensync-0.22/formats/vformats-xml/xml-vcal.c:1270 #7 0xb7ef5f97 in osync_change_compare_data (leftchange=0x83a9408, rightchange=0x8389568) at /build/mbanck/opensync-0.22/opensync/opensync_changecmds.c:194 #8 0xb7ed3947 in _osengine_mapping_find (engine=0x80d4c48, entry=0x8389530) at /build/mbanck/opensync-0.22/osengine/osengine_mapcmds.c:251 #9 osengine_change_map (engine=0x80d4c48, entry=0x8389530) at /build/mbanck/opensync-0.22/osengine/osengine_mapcmds.c:267 #10 0xb7ed51b7 in osengine_mappingentry_decider (engine=0x80d4c48, entry=0x8389530) at /build/mbanck/opensync-0.22/osengine/osengine_deciders.c:62 #11 0xb7ed0206 in engine_message_handler (message=0x83e8ea0, engine=0x80d4c48) at /build/mbanck/opensync-0.22/osengine/osengine_engine.c:322 #12 0xb7efabb2 in _incoming_dispatch (source=0x8370e48, callback=0, user_data=0x836e248) at /build/mbanck/opensync-0.22/opensync/opensync_queue.c:107 #13 0xb7f3fe98 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #14 0xb7f43623 in ?? () from /lib/libglib-2.0.so.0 #15 0xb7f43aea in g_main_loop_run () from /lib/libglib-2.0.so.0 #16 0xb7f6a11f in ?? () from /lib/libglib-2.0.so.0 #17 0xb7b184b5 in start_thread () from /lib/i686/cmov/libpthread.so.0 #18 0xb7e48a5e in clone () from /lib/i686/cmov/libc.so.6 (gdb) INFO:SynCE:device synchronization complete -- Dock Sud BBS http://bbs.docksud.com.ar telnet://bbs.docksud.com.ar ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ SynCE-Devel mailing list SynCE-Devel@... https://lists.sourceforge.net/lists/listinfo/synce-devel |
|
|
Re: segfault on syncI can't solve this for you, but it seems to be related to the date/time
fields. Maybe someone can help you further if you extract those fields from the data you are trying to sync and send them to the list? Best regards, David Eriksson, http://www.divideandconquer.se/ On Mon, 2009-10-19 at 15:40 -0200, Fernando Toledo wrote: > i am in debian testing: > please if need another specific info, tell me. > > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0xb24ceb90 (LWP 14051)] > 0xb7ddd263 in strchr () from /lib/i686/cmov/libc.so.6 > (gdb) bt > #0 0xb7ddd263 in strchr () from /lib/i686/cmov/libc.so.6 > #1 0xb7ef82f5 in osync_time_isutc (vtime=0x0) at > /build/mbanck/opensync-0.22/opensync/opensync_time.c:154 > #2 0xb7fd3aec in osxml_compare_time (leftnode=0xb12f6990, > rightnode=0xb12efff8) at /build/mbanck/opensync-0.22/formats/vformats-xml/xml- > support.c:62 > #3 0xb7fd3fdf in osxml_compare_node (leftnode=0xb12f6990, > rightnode=0xb12efff8) at /build/mbanck/opensync-0.22/formats/vformats-xml/xml- > support.c:177 > #4 0xb7fd3f58 in osxml_compare_node (leftnode=0xb12efdb0, > rightnode=0xb12f6748) at /build/mbanck/opensync-0.22/formats/vformats-xml/xml- > support.c:182 > #5 0xb7fd43ee in osxml_compare (leftinpdoc=0xb11e37a0, > rightinpdoc=0xb1209ec0, scores=0xb24ce124, default_score=0, treshold=99) > at /build/mbanck/opensync-0.22/formats/vformats-xml/xml-support.c:335 > #6 0xb5575250 in compare_vevent (leftchange=0x83a9408, rightchange=0x8389568) > at /build/mbanck/opensync-0.22/formats/vformats-xml/xml-vcal.c:1270 > #7 0xb7ef5f97 in osync_change_compare_data (leftchange=0x83a9408, > rightchange=0x8389568) at > /build/mbanck/opensync-0.22/opensync/opensync_changecmds.c:194 > #8 0xb7ed3947 in _osengine_mapping_find (engine=0x80d4c48, entry=0x8389530) > at /build/mbanck/opensync-0.22/osengine/osengine_mapcmds.c:251 > #9 osengine_change_map (engine=0x80d4c48, entry=0x8389530) at > /build/mbanck/opensync-0.22/osengine/osengine_mapcmds.c:267 > #10 0xb7ed51b7 in osengine_mappingentry_decider (engine=0x80d4c48, > entry=0x8389530) at > /build/mbanck/opensync-0.22/osengine/osengine_deciders.c:62 > #11 0xb7ed0206 in engine_message_handler (message=0x83e8ea0, engine=0x80d4c48) > at /build/mbanck/opensync-0.22/osengine/osengine_engine.c:322 > #12 0xb7efabb2 in _incoming_dispatch (source=0x8370e48, callback=0, > user_data=0x836e248) at > /build/mbanck/opensync-0.22/opensync/opensync_queue.c:107 > #13 0xb7f3fe98 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 > #14 0xb7f43623 in ?? () from /lib/libglib-2.0.so.0 > #15 0xb7f43aea in g_main_loop_run () from /lib/libglib-2.0.so.0 > #16 0xb7f6a11f in ?? () from /lib/libglib-2.0.so.0 > #17 0xb7b184b5 in start_thread () from /lib/i686/cmov/libpthread.so.0 > #18 0xb7e48a5e in clone () from /lib/i686/cmov/libc.so.6 > (gdb) INFO:SynCE:device synchronization complete > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ SynCE-Devel mailing list SynCE-Devel@... https://lists.sourceforge.net/lists/listinfo/synce-devel -- ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ SynCE-Devel mailing list SynCE-Devel@... https://lists.sourceforge.net/lists/listinfo/synce-devel |
|
|
Re: segfault on syncOn Mon, 2009-10-19 at 21:08 +0200, David Eriksson wrote:
> I can't solve this for you, but it seems to be related to the date/time > fields. Maybe someone can help you further if you extract those fields > from the data you are trying to sync and send them to the list? > > Best regards, > > David Eriksson, http://www.divideandconquer.se/ > > And what is this backtrace actually from ? Mark > On Mon, 2009-10-19 at 15:40 -0200, Fernando Toledo wrote: > > i am in debian testing: > > please if need another specific info, tell me. > > > > > > Program received signal SIGSEGV, Segmentation fault. > > [Switching to Thread 0xb24ceb90 (LWP 14051)] > > 0xb7ddd263 in strchr () from /lib/i686/cmov/libc.so.6 > > (gdb) bt > > #0 0xb7ddd263 in strchr () from /lib/i686/cmov/libc.so.6 > > #1 0xb7ef82f5 in osync_time_isutc (vtime=0x0) at > > /build/mbanck/opensync-0.22/opensync/opensync_time.c:154 > > #2 0xb7fd3aec in osxml_compare_time (leftnode=0xb12f6990, > > rightnode=0xb12efff8) at /build/mbanck/opensync-0.22/formats/vformats-xml/xml- > > support.c:62 > > #3 0xb7fd3fdf in osxml_compare_node (leftnode=0xb12f6990, > > rightnode=0xb12efff8) at /build/mbanck/opensync-0.22/formats/vformats-xml/xml- > > support.c:177 > > #4 0xb7fd3f58 in osxml_compare_node (leftnode=0xb12efdb0, > > rightnode=0xb12f6748) at /build/mbanck/opensync-0.22/formats/vformats-xml/xml- > > support.c:182 > > #5 0xb7fd43ee in osxml_compare (leftinpdoc=0xb11e37a0, > > rightinpdoc=0xb1209ec0, scores=0xb24ce124, default_score=0, treshold=99) > > at /build/mbanck/opensync-0.22/formats/vformats-xml/xml-support.c:335 > > #6 0xb5575250 in compare_vevent (leftchange=0x83a9408, rightchange=0x8389568) > > at /build/mbanck/opensync-0.22/formats/vformats-xml/xml-vcal.c:1270 > > #7 0xb7ef5f97 in osync_change_compare_data (leftchange=0x83a9408, > > rightchange=0x8389568) at > > /build/mbanck/opensync-0.22/opensync/opensync_changecmds.c:194 > > #8 0xb7ed3947 in _osengine_mapping_find (engine=0x80d4c48, entry=0x8389530) > > at /build/mbanck/opensync-0.22/osengine/osengine_mapcmds.c:251 > > #9 osengine_change_map (engine=0x80d4c48, entry=0x8389530) at > > /build/mbanck/opensync-0.22/osengine/osengine_mapcmds.c:267 > > #10 0xb7ed51b7 in osengine_mappingentry_decider (engine=0x80d4c48, > > entry=0x8389530) at > > /build/mbanck/opensync-0.22/osengine/osengine_deciders.c:62 > > #11 0xb7ed0206 in engine_message_handler (message=0x83e8ea0, engine=0x80d4c48) > > at /build/mbanck/opensync-0.22/osengine/osengine_engine.c:322 > > #12 0xb7efabb2 in _incoming_dispatch (source=0x8370e48, callback=0, > > user_data=0x836e248) at > > /build/mbanck/opensync-0.22/opensync/opensync_queue.c:107 > > #13 0xb7f3fe98 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 > > #14 0xb7f43623 in ?? () from /lib/libglib-2.0.so.0 > > #15 0xb7f43aea in g_main_loop_run () from /lib/libglib-2.0.so.0 > > #16 0xb7f6a11f in ?? () from /lib/libglib-2.0.so.0 > > #17 0xb7b184b5 in start_thread () from /lib/i686/cmov/libpthread.so.0 > > #18 0xb7e48a5e in clone () from /lib/i686/cmov/libc.so.6 > > (gdb) INFO:SynCE:device synchronization complete > > > > > > ------------------------------------------------------------------------------ > > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > > is the only developer event you need to attend this year. Jumpstart your > > developing skills, take BlackBerry mobile applications to market and stay > > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > > http://p.sf.net/sfu/devconference > > _______________________________________________ SynCE-Devel mailing list SynCE-Devel@... https://lists.sourceforge.net/lists/listinfo/synce-devel > -- ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ SynCE-Devel mailing list SynCE-Devel@... https://lists.sourceforge.net/lists/listinfo/synce-devel |
|
|
Re: segfault on syncOn Mié 21 Oct 2009 11:28:33 Mark Ellis escribió:
> On Mon, 2009-10-19 at 21:08 +0200, David Eriksson wrote: > > I can't solve this for you, but it seems to be related to the date/time > > fields. Maybe someone can help you further if you extract those fields > > from the data you are trying to sync and send them to the list? i can't understand (sorry my english) how to extract these fields? maybe, exporting my calendar as ics or my contact as vcf files? > > > > Best regards, > > > > David Eriksson, http://www.divideandconquer.se/ > > And what is this backtrace actually from ? > > Mark its from msynctool i can't detect what cause it im attach the msynctool --sync output im use synce-opensync-plugin and kdepim-plugin on debian testing/unstable my kdepim is using akonadi for calendar and contacts Note: few day ago, my country don't change the DST and the debian tzdata was out of date. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551195 now i have my tzdata up to date but the problem persist. another data that can i send here , please tell me. thanks you for response. -- Dock Sud BBS http://bbs.docksud.com.ar telnet://bbs.docksud.com.ar ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ SynCE-Devel mailing list SynCE-Devel@... https://lists.sourceforge.net/lists/listinfo/synce-devel |
|
|
Re: segfault on syncOn Thu, 2009-10-22 at 19:02 +0200, Fernando Toledo wrote:
> On Mié 21 Oct 2009 11:28:33 Mark Ellis escribió: > > On Mon, 2009-10-19 at 21:08 +0200, David Eriksson wrote: > > > I can't solve this for you, but it seems to be related to the date/time > > > fields. Maybe someone can help you further if you extract those fields > > > from the data you are trying to sync and send them to the list? > i can't understand (sorry my english) > how to extract these fields? > maybe, exporting my calendar as ics or my contact as vcf files? > > > > > > Best regards, > > > > > > David Eriksson, http://www.divideandconquer.se/ > > > > And what is this backtrace actually from ? > > > > Mark > its from msynctool i can't detect what cause it > > im attach the msynctool --sync output > im use synce-opensync-plugin and kdepim-plugin on debian testing/unstable > my kdepim is using akonadi for calendar and contacts > > Note: few day ago, my country don't change the DST and the debian tzdata was > out of date. > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551195 > now i have my tzdata up to date but the problem persist. > > another data that can i send here , please tell me. > thanks you for response. > msynctool --showgroup <syncgroupname> msynctool --sync <syncgroupname> synce-matchmaker status synce-pstatus Mark ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ SynCE-Devel mailing list SynCE-Devel@... https://lists.sourceforge.net/lists/listinfo/synce-devel |
| Free embeddable forum powered by Nabble | Forum Help |