aMule Forum

English => Backtraces => Topic started by: werner on January 23, 2004, 10:07:18 PM

Title: 1.2.4 crash while moving A4AFs
Post by: werner on January 23, 2004, 10:07:18 PM

Versions:

aMule 1.2.4
wxWindows 2.4.1
GTK 1.2.10
gcc 3.2 20020903 (Red Hat Linux 8.0 3.2-7)
libc 2.3.2 (2003-11-05)
libstdc++ 3.2 (libstdc++.so.5.0.1)

What I did:

I was clicking through a sequence of files, asking for each of them
to "Swap every A4AF to this file now".

What gdb said:

Program received signal SIGSEGV, Segmentation fault.
0x0806ff04 in CEMSocket::IsConnected() (this=0x0) at EMSocket.h:47
47              bool    IsConnected() { return byConnected==ES_CONNECTED;};

Backtraces in attachment.

- Werner

Title: Re: 1.2.4 crash while moving A4AFs
Post by: deltaHF on January 23, 2004, 10:20:54 PM

is there a way that u update your wxGTK ?

Title: Re: 1.2.4 crash while moving A4AFs
Post by: werner on January 23, 2004, 10:34:13 PM

Quote

Originally posted by deltaHF
is there a way that u update your wxGTK ?

I can try :-) What should I use ?

- Werner

Title: Re: 1.2.4 crash while moving A4AFs
Post by: deltaHF on January 23, 2004, 10:39:08 PM

2.4.2 ..  :)

Title: Re: 1.2.4 crash while moving A4AFs
Post by: werner on January 24, 2004, 07:56:58 PM

Quote

Originally posted by deltaHF
2.4.2 ..  :)

Hmm yes, now that you mention it ... 8)

Oddly enough, the RPMs left me with a completely unusable
installation (might be rpm's fault), but rebuilding from sources
did the trick.

Thanks,
- Werner

Title: Re: 1.2.4 crash while moving A4AFs
Post by: deltaHF on January 24, 2004, 08:09:14 PM

hm, rpm -Uvh wxGTK...... should do it too..
ok, but fine if it works now :)

greets

Title: same kind of 1.2.4 crash (with wx 2.4.2)
Post by: werner on January 24, 2004, 09:54:31 PM

A new one. This time, aMule was basically left alone. Could be that
a display redraw was going on at the time of the crash.

Same versions as above, just wx* has been updated, as described
previously in the thread.

Program received signal SIGSEGV, Segmentation fault.
0x0806fff0 in CEMSocket::IsConnected() (this=0x0) at EMSocket.h:47
47              bool    IsConnected() { return byConnected==ES_CONNECTED;};

Backtraces attached.

- Werner

Title: more of the same
Post by: werner on January 25, 2004, 10:18:04 PM

After 23h50, system was unattended at the time of the crash. Same
parameters as before.

Program received signal SIGSEGV, Segmentation fault.
0x0806fff0 in CEMSocket::IsConnected() (this=0x0) at EMSocket.h:47
47              bool    IsConnected() { return byConnected==ES_CONNECTED;};

Backtraces attached.

- Werner