Re: [Opensync-users] Segfault on CLI or Application quit unexpectedly on GUI

[Ademar de S. R. Jr. <ad...@ma...>]

Mariano L=C3=B3pez Reta wrote:
> On Sat, 2006-03-11 at 12:46 +0100, Armin Bauer wrote:
>=20
>>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
>=20
> Hello, Armin:
>=20
> I'm sending this to you and the list, since I'm not sure you meant "sen=
d
> me" literally ;)
>=20
> Is this what you need? I'm sorry if not (I haven't used gdb before).
>=20
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 46912498464928 (LWP 28003)]
> 0x00002aaaaabd1718 in osync_member_initialize (member=3D0x0,
> error=3D0x7fffff86b788) at opensync_member.c:982
> 982             if (!(member->plugindata =3D functions.initialize(membe=
r,
> error))) {
>=20

Armin probably wants a backtrace: use the bt command from
gdb as soon as you get the core. The backtrace contains
the list of functions called up to the point where you
get this SIGSEGV. (This fragment may be enough for him of
course, but just in case...)

Best regards,
  - Ademar

--=20
Ademar de Souza Reis Jr.
Mandriva Conectiva - http://www.mandriva.com.br

^[:wq!