aMule Forum

English => Backtraces => Topic started by: Tsiolkovsky on June 20, 2011, 09:40:28 AM

Title: r10582 - Crash in CSocketSet::Detected
Post by: Tsiolkovsky on June 20, 2011, 09:40:28 AM

I left amuled + amuleweb running over night and when I returned from work I saw that aMule has crashed with the following backtrace:

Code: [Select]

Program received signal SIGSEGV, Segmentation fault.
0x0000000000430e8f in CSocketSet::Detected (this=0x2714a90, read=&virtual table offset 16, write=&virtual table offset 24) at amuled.cpp:278
278     amuled.cpp: No such file or directory.
        in amuled.cpp
(gdb) thread apply all bt

Thread 4 (Thread 0x7fa0f7f72700 (LWP 17451)):
#0  0x00000036d460f40d in nanosleep () from /lib64/libpthread.so.0
#1  0x00000036dd6eb94c in wxMicroSleep(unsigned long) () from /usr/lib64/libwx_baseu-2.8.so.0
#2  0x00000000004c0b3e in UploadBandwidthThrottler::Entry (this=0x3fa0c10) at UploadBandwidthThrottler.cpp:323
#3  0x00000036dd6e716b in wxThreadInternal::PthreadStart(wxThread*) () from /usr/lib64/libwx_baseu-2.8.so.0
#4  0x00000036d4607e6c in start_thread () from /lib64/libpthread.so.0
#5  0x00000036d3ed533d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fa0f6f70700 (LWP 17462)):
#0  0x00000036d460c0cb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00000036dd6e5c36 in wxConditionInternal::WaitTimeout(unsigned long) () from /usr/lib64/libwx_baseu-2.8.so.0
#2  0x00000036dd6e68f2 in wxSemaphoreInternal::WaitTimeout(unsigned long) () from /usr/lib64/libwx_baseu-2.8.so.0
#3  0x0000000000547f7b in CTimerThread::Entry (this=0x28add30) at Timer.cpp:66
#4  0x00000036dd6e716b in wxThreadInternal::PthreadStart(wxThread*) () from /usr/lib64/libwx_baseu-2.8.so.0
#5  0x00000036d4607e6c in start_thread () from /lib64/libpthread.so.0
#6  0x00000036d3ed533d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fa0f8428720 (LWP 17445)):
#0  0x0000000000430e8f in CSocketSet::Detected (this=0x2714a90, read=&virtual table offset 16, write=&virtual table offset 24) at amuled.cpp:278
#1  0x0000000000430f35 in CAmuledGSocketFuncTable::RunSelect (this=0x2715000) at amuled.cpp:308
#2  0x0000000000431284 in CamuleDaemonApp::OnRun (this=0x2714b30) at amuled.cpp:631
#3  0x00000036dd69943b in wxEntry(int&, wchar_t**) () from /usr/lib64/libwx_baseu-2.8.so.0
#4  0x000000000042c7d2 in main (argc=1, argv=<value optimized out>) at amuled.cpp:108
Other packages on system:
wxGTK-2.8.12.0
crypto++-5.6.1
zlib-1.2.5
gd-2.0.35
geoip-1.4.7
libupnp-1.6.6
libpng-1.4.7
libXtst-1.2.0

Title: Re: r10582 - Crash in CSocketSet::Detected
Post by: Stu Redman on June 21, 2011, 08:21:55 PM

Did this ever happen with versions before 10582 ?

Title: Re: r10582 - Crash in CSocketSet::Detected
Post by: Tsiolkovsky on June 22, 2011, 07:43:29 AM

I don't remember seeing this with r10540. But it may be that it happened and I just didn't have GDB attached to it so I didn't catch it.

Title: Re: r10582 - Crash in CSocketSet::Detected
Post by: Stu Redman on June 22, 2011, 12:36:18 PM

I'm asking because just in 10582 there was a change in amuled's socket code, and I haven't seen such a backtrace before.

Title: Re: r10582 - Crash in CSocketSet::Detected
Post by: adaptee on June 30, 2011, 04:33:40 PM

I have similar problem since svn-10582 and have filed a bug report
http://bugs.amule.org/bug_view_advanced_page.php?bug_id=1677

Just to emphasize, this crash is more likely to happen when external connection is estabelished.