Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[pil0t]

Hello,

I updated my server toFreeBSD 5.4 and compiled wxbase 2.6.0 and amule 2.0.0 in a jail with only the base distribution installed. amuled starts but catches an abort when the first connection is made. From the trace it looks like the problem is in wxbase and not in amule. Did anybody already see this behaviour?

Code: [Select]

(gdb) bt
#0  0x281ae31b in pthread_testcancel () from /usr/lib/libpthread.so.1
#1  0x2819f145 in sigaction () from /usr/lib/libpthread.so.1
#2  0x281991dd in pthread_kill () from /usr/lib/libpthread.so.1
#3  0x28198bac in raise () from /usr/lib/libpthread.so.1
#4  0x28474c1b in abort () from /lib/libc.so.5
#5  0x28270d9e in wxFatalSignalHandler ()
   from /tmp/amule/lib/libwx_base-2.6.so.0
#6  0x2819de26 in sigaction () from /usr/lib/libpthread.so.1
#7  0x2819dcab in sigaction () from /usr/lib/libpthread.so.1
#8  0x2819e86c in sigaction () from /usr/lib/libpthread.so.1
#9  0x281a7094 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1
#10 0x281a6f88 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1
#11 0x28460253 in _ctx_start () from /lib/libc.so.5
#12 0x00000000 in ?? ()
#13 0xbfa87c80 in ?? ()
#14 0xbfa879c0 in ?? ()
#15 0x00000000 in ?? ()
#16 0x281a6f24 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1
#16 0x281a6f24 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1
#17 0x282b5ed9 in wxSocketBase::_Wait ()
   from /tmp/amule/lib/libwx_base_net-2.6.so.0
#18 0x282b7105 in wxSocketClient::WaitOnConnect ()
   from /tmp/amule/lib/libwx_base_net-2.6.so.0
#19 0x080f8d59 in CServerSocketHandler::Entry (this=0x8a6ba60)
    at ServerSocket.cpp:127
#20 0x2826ae5d in wxThreadInternal::PthreadStart ()
   from /tmp/amule/lib/libwx_base-2.6.so.0
#21 0x2826aec3 in wxPthreadStart () from /tmp/amule/lib/libwx_base-2.6.so.0
#22 0x2819aaf1 in pthread_create () from /usr/lib/libpthread.so.1
#23 0x28460253 in _ctx_start () from /lib/libc.so.5


[thedude0001]

Moved to --> Backtraces  

[Mr Faber]

Hm, I am not sure but aMule needs wxGTK. WxBase can be used for aMuled but not for the monolithic as far as I know.

cu
Mr Faber

[ken]

What were the lines above the "(gdb)" prompt and the backtrace you posted?  It looks to me like this is probably just a benign signal (probably SIGPIPE) being caught and gdb is just stopping to let you look.  Put:

handle SIGPIPE noprint nostop pass

into your ~/.gdbinit so that gdb will ignore this benign signal.

[pil0t]

The signal was an ABORT. My trace was created by starting gdb, loading amuled (file amuled), loading the core (core-file amuled-core) and then doing the backtrace. I compiled wxBase and amuled with the following configure lines:

Code: [Select]

wxBase:
./configure --prefix=/tmp/amule --enable-optimise --disable-compat24 --disable-compat22
amuled:
./configure --prefix=/tmp/amule --enable-optimize --disable-monolithic --enable-amule-daemon --enable-amulecmd --disable-nls --with-wx-config=/tmp/amule/bin/wx-config
The system is FBSD 5.4 base system in a Jail (strict chroot environment) with no additional packages installed. The monolithic amule is running perfect in a Jail, but I use a precompiled wxgtk-2.4.2_8 and tons of precompiled X packages to compile/run it.

[ken]

OK, nevermind me.  Clearly, I don't know what I'm talking about.  :]