From: Jason G. <ju...@lo...> - 2006-05-21 03:53:24
|
Regarding the crash reported by a couple of folks around the 13th (see "Crash with invalid pointer when using evo plugin under fc5"), apart from the stack trace already provided, are there any more diagnostics that I can provide to help with fault diagnosis? It's easy for me to reproduce the crash - opensync the only time opensync doesn't crash when syncing with evo is when there are no contacts! So I'm in a good position to provide whatever info will be helpful. Thanks, Jason. |
From: Marcos \Japa\ U. <th...@gm...> - 2006-05-21 04:22:49
|
SSBjYW4gZWFzaWx5IHJlcHJvZHVjZSB0aGUgYnVnLCBpbiBGZWRvcmEgNQoKSSBiZWxpZXZlIGFu b3RoZXIgdXNlciBmcm9tIGgyMjAwIHVzaW5nIEdlbnRvbyBjYW4gcmVwcm9kdWNlIGl0IHRvby4K CkJ0dywgSSBjYW4gcmVwcm9kdWNlIGJ1ZyB1c2luZyBhIGV2bzJmaWxlIHN5bmMgdG9vLiBJIHdh bnQgdG8gaGVscC4KCk9uIDUvMjEvMDYsIEphc29uIEdyYW50IDxqdW5rQGxvZ3VsYXIuY29tPiB3 cm90ZToKPgo+ICBSZWdhcmRpbmcgdGhlIGNyYXNoIHJlcG9ydGVkIGJ5IGEgY291cGxlIG9mIGZv bGtzIGFyb3VuZCB0aGUgMTN0aCAoc2VlCj4gIkNyYXNoIHdpdGggaW52YWxpZCBwb2ludGVyIHdo ZW4gdXNpbmcgZXZvIHBsdWdpbiB1bmRlciBmYzUiKSwgYXBhcnQgZnJvbQo+IHRoZSBzdGFjayB0 cmFjZSBhbHJlYWR5IHByb3ZpZGVkLCBhcmUgdGhlcmUgYW55IG1vcmUgZGlhZ25vc3RpY3MgdGhh dCBJIGNhbgo+IHByb3ZpZGUgdG8gaGVscCB3aXRoIGZhdWx0IGRpYWdub3Npcz8gIEl0J3MgZWFz eSBmb3IgbWUgdG8gcmVwcm9kdWNlIHRoZQo+IGNyYXNoIC0gb3BlbnN5bmMgdGhlIG9ubHkgdGlt ZSBvcGVuc3luYyBkb2Vzbid0IGNyYXNoIHdoZW4gc3luY2luZyB3aXRoIGV2bwo+IGlzIHdoZW4g dGhlcmUgYXJlIG5vIGNvbnRhY3RzISAgU28gSSdtIGluIGEgZ29vZCBwb3NpdGlvbiB0byBwcm92 aWRlCj4gd2hhdGV2ZXIgaW5mbyB3aWxsIGJlIGhlbHBmdWwuCj4KPiAgVGhhbmtzLAo+Cj4gIEph c29uLgo= |
From: Armin B. <arm...@de...> - 2006-06-02 20:25:10
Attachments:
signature.asc
|
Hi, the problem I have with evolution is: it crashes here (debian) as well or it doesnt work. I tried to trace the bug, but it is definitely inside evolution. I heard reports that very new versions of eds and evolution work correctly but i wasnt yet able to verify them. Armin Marcos "Japa" Umino wrote: > I can easily reproduce the bug, in Fedora 5 >=20 > I believe another user from h2200 using Gentoo can reproduce it too. >=20 > Btw, I can reproduce bug using a evo2file sync too. I want to help. >=20 > On 5/21/06, Jason Grant <ju...@lo...> wrote: >> >> Regarding the crash reported by a couple of folks around the 13th (se= e >> "Crash with invalid pointer when using evo plugin under fc5"), apart f= rom >> the stack trace already provided, are there any more diagnostics that >> I can >> provide to help with fault diagnosis? It's easy for me to reproduce t= he >> crash - opensync the only time opensync doesn't crash when syncing >> with evo >> is when there are no contacts! So I'm in a good position to provide >> whatever info will be helpful. >> >> Thanks, >> >> Jason. > R=C8=A7=EF=BF=BD:&q=EF=BF=BD[=EF=BF=BD=EF=BF=BD=EF=BF=BDy=EF=BF=BDhv=EF= =BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD^y=EF=BF=BDh=EF=BF=BD=EF=BF=BDi=EF=BF=BD= =EF=BF=BDpy=EF=BF=BD=1E=EF=BF=BD=EF=BF=BDz=EF=BF=BD=1Er=EF=BF=BD=EF=BF=BD= !=EF=BF=BD=EF=BF=BD=EF=BF=BDn}=EF=BF=BDh=EF=BF=BD=EA=AE=89=EF=BF=BD%=EF=BF= =BD=08=EF=BF=BD=EF=BF=BD=EF=BF=BD=DE=8A{^=EF=BF=BD=EF=BF=BD=EF=BF=BDy=EF=BF= =BD^r=19=E8=96=88 > 2=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EC=A8=BA=EF=BF=BD=EF=BF=BDm=E6=AC= =89=EF=BF=BD=C3=A3 =E5=A1=A7H=04=C5=9Em*az=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF= =BF=BDbq=EF=BF=BDb=EF=BF=BDt=EF=BF=BD=EF=BF=BD=EF=BF=BD]5m=EF=BF=BD=1Ev=EF= =BF=BD=EF=BF=BD=EF=BF=BD!xg=EF=BF=BD=EF=BF=BDx=EF=BF=BD=EF=BF=BD=1B > m=EF=BF=BD=EF=BF=BD=EF=BF=BDzV=EF=BF=BD=EF=BF=BD=EF=BF=BD=DA=96F=EF=BF=BD= =EF=BF=BD=EF=BF=BD=7F=EF=BF=BD=EF=BF=BD\=EF=BF=BD=D0=9EI"t > =D3=BD=3Dn'=DB=AD=EF=BF=BD=EF=BF=BDZ=EF=BF=BD > =D7=AE6:=EF=BF=BD=EF=BF=BD=EF=BF=BD)=DC=BA=C7=AB=EF=BF=BDf=EF=BF=BD=EF=BF= =BD)=EF=BF=BD+-:=EF=BF=BD=EF=BF=BD=EF=BF=BD)=DC=BA=C7=AB=EF=BF=BDX=EF=BF=BD= =EF=BF=BD=EF=BF=BD(=EF=BF=BD=EF=BF=BD=1E~=EF=BF=BD=EF=BF=BDzw=EF=BF=BD=EF= =BF=BD=EF=BF=BDi=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BDl=EF=BF=BD=EF=BF=BD=EF= =BF=BDq=EF=BF=BD=EF=BF=BD=07=EF=BF=BDz=EF=BF=BD=EF=BF=BD=EF=BF=BDl=EF=BF=BD= X=EF=BF=BD=EF=BF=BD)=DF=A3=EF=BF=BD)z{2=EF=BF=BD=CB=ACers=3D |
From: Jason G. <ju...@lo...> - 2006-06-15 06:51:46
|
Hi Armin, I'm still experiencing the crash with the new version of Evolution that was released on the Fedora yum sites recently. Looking at the stack trace, it looks to me like it is crashing when opensync is attempting to free an invalid pointer from xml-vcard.so? Here's the stack trace: [sync details omitted] All clients sent changes or error All conflicts have been reported *** glibc detected *** msynctool: munmap_chunk(): invalid pointer: 0x00327b1b *** ======= Backtrace: ========= /lib/libc.so.6(__libc_free+0x17b)[0x3b151f] /usr/lib/libglib-2.0.so.0(g_free+0x31)[0xc1d5a1] /usr/local/lib/opensync/formats/xml-vcard.so[0x320aed] /usr/local/lib/opensync/formats/xml-vcard.so[0x3216fc] /usr/local/lib/opensync/formats/xml-vcard.so[0x31fbed] /usr/local/lib/libopensync.so.0(osync_converter_invoke+0xea)[0x33ed9a] /usr/local/lib/libopensync.so.0(osync_conv_convert_fn+0x16a)[0x33f98a] /usr/local/lib/libopensync.so.0(osync_change_convert_member_sink +0x5d)[0x3401ad] /usr/local/lib/libopensync.so.0(osync_member_commit_change +0xcb)[0x33abfb] /usr/local/lib/libosengine.so.0(client_message_handler+0x196)[0xf27186] /usr/local/lib/libosengine.so.0(_queue_dispatch+0x95)[0xf266f5] /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x16d)[0xc1615d] /usr/lib/libglib-2.0.so.0[0xc193ef] /usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1a9)[0xc19799] /usr/lib/libglib-2.0.so.0[0xc33a1f] /lib/libpthread.so.0[0xdef3b6] /lib/libc.so.6(__clone+0x5e)[0x41233e] On Fri, 2006-06-02 at 22:25 +0200, Armin Bauer wrote: > Hi, > > the problem I have with evolution is: it crashes here (debian) as well > or it doesnt work. I tried to trace the bug, but it is definitely inside > evolution. > > I heard reports that very new versions of eds and evolution work > correctly but i wasnt yet able to verify them. > > Armin > > Marcos "Japa" Umino wrote: > > I can easily reproduce the bug, in Fedora 5 > > > > I believe another user from h2200 using Gentoo can reproduce it too. > > > > Btw, I can reproduce bug using a evo2file sync too. I want to help. > > > > On 5/21/06, Jason Grant <ju...@lo...> wrote: > >> > >> Regarding the crash reported by a couple of folks around the 13th (see > >> "Crash with invalid pointer when using evo plugin under fc5"), apart from > >> the stack trace already provided, are there any more diagnostics that > >> I can > >> provide to help with fault diagnosis? It's easy for me to reproduce the > >> crash - opensync the only time opensync doesn't crash when syncing > >> with evo > >> is when there are no contacts! So I'm in a good position to provide > >> whatever info will be helpful. > >> > >> Thanks, > >> > >> Jason. |