Bug#846061: [Pkg-amule-devel] Bug#846061: (no subject)
According to http://wiki.amule.org/wiki/Backtraces#Compiling_aMule in order for getting gdb backtrace aMule shold be compiled with "--enable-debug --disable-optimize"
Bug#846061: [Pkg-amule-devel] Bug#846061: (no subject)
On Thu, Jan 5, 2017 at 5:30 PM, ederwrote: > No symbol table info available. this shouldnt happen, are you sure you have installed amule and amule-dbg at the same exact version? can you paste the output of `dpkg -l 'amule*'` thanks -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#846061: [Pkg-amule-devel] Bug#846061: (no subject)
On Thu, Jan 5, 2017 at 3:14 PM, ederwrote: > (gdb) bt > #0 0x761cf446 in ?? () from /usr/lib/x86_64-linux-gnu(gdb) bt full > #0 0x761cf446 in ?? () from /usr/lib/x86_64-linux-gnu/ > libwx_gtk2u_core-3.0.so.0 > > (gdb) bt full > #0 0x761cf446 in ?? () from /usr/lib/x86_64-linux-gnu/ > libwx_gtk2u_core-3.0.so.0 > No symbol table info available. > Backtrace stopped: Cannot access memory at address 0x7fffdde8 > > (gdb) thread apply all bt > Couldn't get registers: No existe el proceso. dammit i'm really sorry, but i forgot to ask you to install the amule-dbg package which contains the symbols needed to provide a meaningful backtrace; could you pleae do that and provide the backtrace again? -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#846061: [Pkg-amule-devel] Bug#846061: (no subject)
On Sun, Dec 25, 2016 at 4:33 AM, ederwrote: > Same here. Amule completly unusable because constant crashes. and as i've asked before: please follow the steps at http://wiki.amule.org/wiki/Backtraces#Create_a_backtrace to generate a gdb backtrace and report it back here, thanks -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi