aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Pages: [1] 2

Author Topic: get memory segemtation fault (Speicher zugriffsfehler) starting amule  (Read 10921 times)

MasterKGB

  • Jr. Member
  • **
  • Karma: 1
  • Offline Offline
  • Posts: 51

Hi
running gentoo kernel 2.6.30 and kde 4.2
Amule used from svn problems occoure since 9732 and not changing go forward to 9755 or use the before running 9721
after typing amule in command prompt get (Speicherzugriffsfehler) memory segmentation fault
Created a backtrace (rebuilded crypto++ not help)

Starting program: /usr/local/bin/amule                                       
[Thread debugging using libthread_db enabled]                               
[New Thread 0xb539c720 (LWP 611)]                                           

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb539c720 (LWP 611)]         
0xb7d343ec in CryptoPP::SHA256::InitState () from /usr/lib/libcrypto++.so.0
(gdb) bt                                                                   
#0  0xb7d343ec in CryptoPP::SHA256::InitState () from /usr/lib/libcrypto++.so.0
#1  0x080ea2fc in CryptoPP::IteratedHashWithStaticTransform<unsigned int, CryptoPP::EnumToType<CryptoPP::ByteOrder, 1>, 64u, 32u, CryptoPP::SHA256, 32u, true>::Init (this=0xbf9881c8) at /usr/include/cryptopp/iterhash.h:90
#2  0xb7cdbd33 in CryptoPP::IteratedHashBase<unsigned int, CryptoPP::HashTransformation>::Restart () from /usr/lib/libcrypto++.so.0
#3  0xb7cde0eb in CryptoPP::IteratedHashBase<unsigned int, CryptoPP::HashTransformation>::TruncatedFinal () from /usr/lib/libcrypto++.so.0
#4  0xb7d0f9c6 in CryptoPP::RandomPool::IncorporateEntropy () from /usr/lib/libcrypto++.so.0
#5  0xb7d02972 in CryptoPP::AutoSeededRandomPool::Reseed () from /usr/lib/libcrypto++.so.0
#6  0x08440004 in AutoSeededRandomPool (this=0x88459e0, blocking=false, seedSize=32) at /usr/include/cryptopp/osrng.h:89
#7  0x0843fc13 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at RandomFunctions.cpp:31
#8  0x0843fc4c in global constructors keyed to _Z13GetRandomPoolv () at RandomFunctions.cpp:62
#9  0x084da012 in ?? ()
#10 0xb7f77310 in ?? () from /lib/ld-linux.so.2
#11 0x08648ff4 in ?? ()
#12 0xbf988348 in ?? ()
#13 0x08085215 in _init ()
Backtrace stopped: frame did not save the PC
(gdb) bt full
#0  0xb7d343ec in CryptoPP::SHA256::InitState () from /usr/lib/libcrypto++.so.0
No symbol table info available.
#1  0x080ea2fc in CryptoPP::IteratedHashWithStaticTransform<unsigned int, CryptoPP::EnumToType<CryptoPP::ByteOrder, 1>, 64u, 32u, CryptoPP::SHA256, 32u, true>::Init (this=0xbf9881c8) at /usr/include/cryptopp/iterhash.h:90
No locals.
#2  0xb7cdbd33 in CryptoPP::IteratedHashBase<unsigned int, CryptoPP::HashTransformation>::Restart () from /usr/lib/libcrypto++.so.0
No symbol table info available.
#3  0xb7cde0eb in CryptoPP::IteratedHashBase<unsigned int, CryptoPP::HashTransformation>::TruncatedFinal () from /usr/lib/libcrypto++.so.0
No symbol table info available.
#4  0xb7d0f9c6 in CryptoPP::RandomPool::IncorporateEntropy () from /usr/lib/libcrypto++.so.0
No symbol table info available.
#5  0xb7d02972 in CryptoPP::AutoSeededRandomPool::Reseed () from /usr/lib/libcrypto++.so.0
No symbol table info available.
#6  0x08440004 in AutoSeededRandomPool (this=0x88459e0, blocking=false, seedSize=32) at /usr/include/cryptopp/osrng.h:89
No locals.
#7  0x0843fc13 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at RandomFunctions.cpp:31
No locals.
#8  0x0843fc4c in global constructors keyed to _Z13GetRandomPoolv () at RandomFunctions.cpp:62
No locals.
#9  0x084da012 in ?? ()
No symbol table info available.
#10 0xb7f77310 in ?? () from /lib/ld-linux.so.2
No symbol table info available.
#11 0x08648ff4 in ?? ()
No symbol table info available.
#12 0xbf988348 in ?? ()
No symbol table info available.
#13 0x08085215 in _init ()
No symbol table info available.
Backtrace stopped: frame did not save the PC
(gdb) thread apply all bt

Thread 1 (Thread 0xb539c720 (LWP 611)):
#0  0xb7d343ec in CryptoPP::SHA256::InitState () from /usr/lib/libcrypto++.so.0
#1  0x080ea2fc in CryptoPP::IteratedHashWithStaticTransform<unsigned int, CryptoPP::EnumToType<CryptoPP::ByteOrder, 1>, 64u, 32u, CryptoPP::SHA256, 32u, true>::Init (this=0xbf9881c8) at /usr/include/cryptopp/iterhash.h:90
#2  0xb7cdbd33 in CryptoPP::IteratedHashBase<unsigned int, CryptoPP::HashTransformation>::Restart () from /usr/lib/libcrypto++.so.0
#3  0xb7cde0eb in CryptoPP::IteratedHashBase<unsigned int, CryptoPP::HashTransformation>::TruncatedFinal () from /usr/lib/libcrypto++.so.0
#4  0xb7d0f9c6 in CryptoPP::RandomPool::IncorporateEntropy () from /usr/lib/libcrypto++.so.0
#5  0xb7d02972 in CryptoPP::AutoSeededRandomPool::Reseed () from /usr/lib/libcrypto++.so.0
#6  0x08440004 in AutoSeededRandomPool (this=0x88459e0, blocking=false, seedSize=32) at /usr/include/cryptopp/osrng.h:89
#7  0x0843fc13 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at RandomFunctions.cpp:31
#8  0x0843fc4c in global constructors keyed to _Z13GetRandomPoolv () at RandomFunctions.cpp:62
#9  0x084da012 in ?? ()
#10 0xb7f77310 in ?? () from /lib/ld-linux.so.2
#11 0x08648ff4 in ?? ()
#12 0xbf988348 in ?? ()
#13 0x08085215 in _init ()
Backtrace stopped: frame did not save the PC

??? Can some help?
Logged

myth

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 38
  • Offline Offline
  • Posts: 570
OT
« Reply #1 on: August 08, 2009, 01:58:43 PM »

....wen man nicht alles wieder trifft :D

Hi MasterKGB!
Logged

MasterKGB

  • Jr. Member
  • **
  • Karma: 1
  • Offline Offline
  • Posts: 51
Re: get memory segemtation fault (Speicher zugriffsfehler) starting amule
« Reply #2 on: August 08, 2009, 03:03:36 PM »

Tjo ;) ich geh nicht verloren ;)

Logged

Stu Redman

  • Administrator
  • Hero Member
  • *****
  • Karma: 214
  • Offline Offline
  • Posts: 3739
  • Engines screaming
Re: get memory segemtation fault (Speicher zugriffsfehler) starting amule
« Reply #3 on: August 08, 2009, 03:11:26 PM »

As you can see, crash occurs deeply inside cryptopp and is probably not related to aMule.
What version of cryptopp are you using? If it's 5.6.0 try using 5.5.2 instead.
Quote
Amule used from svn problems occoure since 9732 and not changing go forward to 9755 or use the before running 9721
Huh ? Is the problem now related to a certain SVN version or not ? (If you have problems with English you can also post in German, but please do it in the German board.)

And please don't post in German here, both of you. The others don't like it. I don't like it either if people post in, say, Finnish.
For the others: It was just a little greeting, nothing of interest.
Logged
The image of mother goddess, lying dormant in the eyes of the dead, the sheaf of the corn is broken, end the harvest, throw the dead on the pyre -- Iron Maiden, Isle of Avalon

MasterKGB

  • Jr. Member
  • **
  • Karma: 1
  • Offline Offline
  • Posts: 51
Re: get memory segemtation fault (Speicher zugriffsfehler) starting amule
« Reply #4 on: August 08, 2009, 04:09:56 PM »

OK, THX changing to crypto++-5.5.2-r1 resolve the problem.

Sorry haven't read that there are problems using the 5.6.0

Quote
Amule used from svn problems occur since 9732 and not changing go forward to 9755 or use the before running 9721

Sorry forgot to type ", and ." it Only mean:
I use the SVN version. My Problem occur since I tried to compile the SVN 9732. Then I tried compiling the 9755 with the same Problem.
Now I tried go back to the SVN 9721 and receive the same message.
After trying to create a Backtrace i saw the problem with crypto++. I recompiled it with no result. Is it written somewhere? The Problem using 5.6?

Sorry for the german greating above, can be deleted!
Logged

Stu Redman

  • Administrator
  • Hero Member
  • *****
  • Karma: 214
  • Offline Offline
  • Posts: 3739
  • Engines screaming
Re: get memory segemtation fault (Speicher zugriffsfehler) starting amule
« Reply #5 on: August 08, 2009, 05:27:48 PM »

Is it written somewhere? The Problem using 5.6?
Just personal experience. I think they are overdoing the optimizations and it's getting out of hand on certain platforms.
Problem is, all those bugs with it are hard to grasp and thus hard to report.

There was a discussion about this issue on the CryptoPP users group, but nothing came from it.
Logged
The image of mother goddess, lying dormant in the eyes of the dead, the sheaf of the corn is broken, end the harvest, throw the dead on the pyre -- Iron Maiden, Isle of Avalon

MasterKGB

  • Jr. Member
  • **
  • Karma: 1
  • Offline Offline
  • Posts: 51
Re: get memory segemtation fault (Speicher zugriffsfehler) starting amule
« Reply #6 on: August 08, 2009, 06:03:24 PM »

Maybe create for amule a bad list of packages ;)

Only a joke, cause much time needed for that.
Logged

GonoszTopi

  • The current man in charge of most things.
  • Administrator
  • Hero Member
  • *****
  • Karma: 169
  • Offline Offline
  • Posts: 2685
Re: get memory segemtation fault (Speicher zugriffsfehler) starting amule
« Reply #7 on: August 08, 2009, 06:26:41 PM »

(rebuilded crypto++ not help)
I hope you know (and did) that after rebuilding Crypto++ you must also rebuild aMule.

nothing of interest.
Move on, nothing to see here! ;)
Logged
concordia cum veritate

MasterKGB

  • Jr. Member
  • **
  • Karma: 1
  • Offline Offline
  • Posts: 51
Re: get memory segemtation fault (Speicher zugriffsfehler) starting amule
« Reply #8 on: August 08, 2009, 06:43:50 PM »

Yes of course I know and done
And tried 5.6.0 an 5.6.0-r1

Both not working
Logged

Stu Redman

  • Administrator
  • Hero Member
  • *****
  • Karma: 214
  • Offline Offline
  • Posts: 3739
  • Engines screaming
Re: get memory segemtation fault (Speicher zugriffsfehler) starting amule
« Reply #9 on: August 08, 2009, 07:40:19 PM »

Please try the following patch with 5.6.0 (or 5.6.0-r1) and tell me if it fixes the problem.
Logged
The image of mother goddess, lying dormant in the eyes of the dead, the sheaf of the corn is broken, end the harvest, throw the dead on the pyre -- Iron Maiden, Isle of Avalon

MasterKGB

  • Jr. Member
  • **
  • Karma: 1
  • Offline Offline
  • Posts: 51
Re: get memory segemtation fault (Speicher zugriffsfehler) starting amule
« Reply #10 on: August 22, 2009, 01:13:06 PM »

have I done something wrong?
tried to emerge crypto-5.6.0-r1 with that patch and got that output:
Quote
***** crypto++-5.6.0-rng.patch *****

====================================

PATCH COMMAND:   patch -p0 -g0 -E --no-backup-if-mismatch < /usr/portage/dev-libs/crypto++/files/crypto++-5.6.0-rng.patch

====================================
(Stripping trailing CRs from patch.)
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: RandomFunctions.cpp
|===================================================================
|--- RandomFunctions.cpp        (revision 9749)
|+++ RandomFunctions.cpp        (working copy)
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
(Stripping trailing CRs from patch.)
can't find file to patch at input line 53
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: RandomFunctions.h
|===================================================================
|--- RandomFunctions.h  (revision 9749)
|+++ RandomFunctions.h  (working copy)
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
====================================

If done it in the section src_prepare (fyi)
« Last Edit: August 22, 2009, 01:14:38 PM by MasterKGB »
Logged

GonoszTopi

  • The current man in charge of most things.
  • Administrator
  • Hero Member
  • *****
  • Karma: 169
  • Offline Offline
  • Posts: 2685
Re: get memory segemtation fault (Speicher zugriffsfehler) starting amule
« Reply #11 on: August 22, 2009, 02:35:24 PM »

This patch is for aMule, not for Crypto++.
Logged
concordia cum veritate

DarkNRG

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 4
Re: get memory segemtation fault (Speicher zugriffsfehler) starting amule
« Reply #12 on: August 29, 2009, 03:56:54 PM »

I had a similar problem with aMule and crypto++ and could solve it by enabling SSE3 support in crypto++ despite my cpu doesn't support sse3 according to /proc/cpuinfo.

PS: I'm using gentoo so maybe it was some gentoo-specific patch of crypto++ which didn't like aMule.
Logged

Stu Redman

  • Administrator
  • Hero Member
  • *****
  • Karma: 214
  • Offline Offline
  • Posts: 3739
  • Engines screaming
Re: get memory segemtation fault (Speicher zugriffsfehler) starting amule
« Reply #13 on: September 16, 2009, 10:04:00 PM »

Please try the following patch with 5.6.0 (or 5.6.0-r1) and tell me if it fixes the problem.
Now what? Still around?
I hate it when people come and ask for help and then drop away again.  >:(
Logged
The image of mother goddess, lying dormant in the eyes of the dead, the sheaf of the corn is broken, end the harvest, throw the dead on the pyre -- Iron Maiden, Isle of Avalon

wires

  • Jr. Member
  • **
  • Karma: 6
  • Offline Offline
  • Posts: 83
Re: get memory segemtation fault (Speicher zugriffsfehler) starting amule
« Reply #14 on: September 17, 2009, 09:30:36 AM »

I'm not suffering this issue but patch applied to SVN 9803 and amule is still working. At least you have a regression test on AMD64 arch (Fedora 11)

Edit: cryptopp-5.6.0-1.fc11.x86_64

Cheers
Logged
Pages: [1] 2