aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Sabayon 5.2 - No GUI at aMule startup.  (Read 2073 times)

tekwyzrd

  • Approved Newbie
  • *
  • Karma: 2
  • Offline Offline
  • Posts: 18
Sabayon 5.2 - No GUI at aMule startup.
« on: June 04, 2010, 07:17:13 AM »

It's been a couple months now since amule worked on my athlon xp 2600+. I've tried the crypto++ and amule from portage and entropy with the same results. System monitor shows amule running but no gui. I terminated it in system monitor.

The following is from amule 2.2.6 emerged today

$ gdb /usr/bin/amule

warning: Can not parse XML syscalls information; XML support was disabled at compile time.
GNU gdb (Gentoo 7.0 p1) 7.0
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>...
Reading symbols from /usr/bin/amule...Reading symbols from /usr/lib/debug/usr/bin/amule.debug...done.
(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/amule
[Thread debugging using libthread_db enabled]

Program received signal SIGTERM, Terminated.
0xb7d9987d in ?? () from /usr/lib/libcrypto++.so.0
(gdb) bt
#0  0xb7d9987d in ?? () from /usr/lib/libcrypto++.so.0
Cannot access memory at address 0xcf4d2071
(gdb) bt full
#0  0xb7d9987d in ?? () from /usr/lib/libcrypto++.so.0
No symbol table info available.
Cannot access memory at address 0xcf4d2071
(gdb) thread apply all bt

Thread 1 (Thread 0xb4ee4720 (LWP 17969)):
#0  0xb7d9987d in ?? () from /usr/lib/libcrypto++.so.0
Cannot access memory at address 0xcf4d2071
(gdb)

compiled manually using 2.2.6 source tarball

warning: Can not parse XML syscalls information; XML support was disabled at compile time.
GNU gdb (Gentoo 7.0 p1) 7.0
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>...
Reading symbols from /usr/bin/amule...done.
(gdb) run
Starting program: /usr/bin/amule
[Thread debugging using libthread_db enabled]

Program received signal SIGTERM, Terminated.
0xb7d998df in ?? () from /usr/lib/libcrypto++.so.0
(gdb) bt
#0  0xb7d998df in ?? () from /usr/lib/libcrypto++.so.0
Cannot access memory at address 0x1e4c1cea
(gdb) bt full
#0  0xb7d998df in ?? () from /usr/lib/libcrypto++.so.0
No symbol table info available.
Cannot access memory at address 0x1e4c1cea
(gdb) thread apply all bt

Thread 1 (Thread 0xb4f18720 (LWP 18836)):
#0  0xb7d998df in ?? () from /usr/lib/libcrypto++.so.0
Cannot access memory at address 0x1e4c1cea
(gdb)

I posted to the sabayon forum too forum too.
Logged

tekwyzrd

  • Approved Newbie
  • *
  • Karma: 2
  • Offline Offline
  • Posts: 18
Re: Sabayon 5.2 - No GUI at aMule startup.
« Reply #1 on: June 04, 2010, 08:58:04 AM »

the gentoo bug squashers have marked the crypto++ problem fixed but it's obviously not.

re-emerged current gentoo crypto++-5.6.0-r1 and amule 2.2.6

gdb /usr/bin/amule

warning: Can not parse XML syscalls information; XML support was disabled at compile time.
GNU gdb (Gentoo 7.0 p1) 7.0
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>...
Reading symbols from /usr/bin/amule...Reading symbols from /usr/lib/debug/usr/bin/amule.debug...done.
(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/amule
[Thread debugging using libthread_db enabled]
^C
Program received signal SIGINT, Interrupt.
0xb7d99a31 in CryptoPP::X86_SHA256_HashBlocks(unsigned int*, unsigned int const*, unsigned int) () from /usr/lib/libcrypto++.so.0
(gdb) bt
#0  0xb7d99a31 in CryptoPP::X86_SHA256_HashBlocks(unsigned int*, unsigned int const*, unsigned int) () from /usr/lib/libcrypto++.so.0
Cannot access memory at address 0x9cfec676
(gdb) bt full
#0  0xb7d99a31 in CryptoPP::X86_SHA256_HashBlocks(unsigned int*, unsigned int const*, unsigned int) () from /usr/lib/libcrypto++.so.0
No symbol table info available.
Cannot access memory at address 0x9cfec676
(gdb) thread apply all bt

Thread 1 (Thread 0xb4ee4720 (LWP 6714)):
#0  0xb7d99a31 in CryptoPP::X86_SHA256_HashBlocks(unsigned int*, unsigned int const*, unsigned int) () from /usr/lib/libcrypto++.so.0
Cannot access memory at address 0x9cfec676
(gdb) kill
Kill the program being debugged? (y or n) y
(gdb)
Logged

GonoszTopi

  • The current man in charge of most things.
  • Administrator
  • Hero Member
  • *****
  • Karma: 169
  • Offline Offline
  • Posts: 2685
Re: Sabayon 5.2 - No GUI at aMule startup.
« Reply #2 on: June 04, 2010, 01:47:10 PM »

See http://forum.amule.org/index.php?topic=17665.msg96388#msg96388 and please report whether it fixes your problem or not.
Logged
concordia cum veritate

tekwyzrd

  • Approved Newbie
  • *
  • Karma: 2
  • Offline Offline
  • Posts: 18
Re: Sabayon 5.2 - No GUI at aMule startup.
« Reply #3 on: June 05, 2010, 09:01:37 AM »

Working with the .tar source for crypt0++-5.6.0 , changing to  -O1 and adding -DCRYPTOPP_DISABLE_ASM to the cxxflags in the gnumakefile results in a build that successfully completes cryptest when run in the source directory. After installing it a  manual build of amule-svn-r10125 outside of portage  fails to start properly. Will post again later in the day after I've emerged a debug enabled copy from portage and built from the latest stable  and svn source.
Logged