Bug 267216 - net-p2p/amule: amuled 2.3.3 core dumps
Summary: net-p2p/amule: amuled 2.3.3 core dumps
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Many People
Assignee: Nuno Teixeira
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-20 02:34 UTC by echoxxzz
Modified: 2024-04-15 19:28 UTC (History)
4 users (show)

See Also:
eduardo: maintainer-feedback-


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description echoxxzz 2022-10-20 02:34:45 UTC
I've tried installing amule using the FreeBSD pkg repo and amuled keeps core dumping as soon as I try and start it.

I've tried building just amuled with nls from ports and it also core dumps.

The only solution I've found to get it to work is to build the security/cryptopp package with SIMD=on.

If I used gdb to try and debug the core dump this is what it shows me:

Core was generated by `./amuled --help'.
Program terminated with signal SIGSEGV, Segmentation fault.
Address not mapped to object.
#0  0x0000000800a8ce35 in ?? () from /usr/local/lib/libcryptopp.so.8
(gdb) where
#0  0x0000000800a8ce35 in ?? () from /usr/local/lib/libcryptopp.so.8
#1  0x0000000800a8dc2f in CryptoPP::SHA256::HashMultipleBlocks(unsigned int const*, unsigned long)
    () from /usr/local/lib/libcryptopp.so.8
#2  0x0000000800a134ff in CryptoPP::IteratedHashBase<unsigned int, CryptoPP::HashTransformation>::Update(unsigned char const*, unsigned long) () from /usr/local/lib/libcryptopp.so.8
#3  0x0000000800a65670 in CryptoPP::RandomPool::IncorporateEntropy(unsigned char const*, unsigned long) () from /usr/local/lib/libcryptopp.so.8
#4  0x0000000800a512bd in CryptoPP::AutoSeededRandomPool::Reseed(bool, unsigned int) ()
   from /usr/local/lib/libcryptopp.so.8
#5  0x00000000003ed098 in _GLOBAL__sub_I_RandomFunctions.cpp ()
#6  0x000000080040f0fd in ?? () from /libexec/ld-elf.so.1
#7  0x0000000000000000 in ?? ()
(gdb)
Comment 1 echoxxzz 2022-10-21 00:44:35 UTC
Now that it at least starts with core dumping it's giving me a new error and just stopping:

20:43:17: Debug: Failed to unregister 33 in direction 1
Assertion failed: ./src/common/fdiodispatcher.cpp:ModifyFD:113: Assertion 'i != m_handlers.end()' failed. modifying unregistered handler?
Backtrace follows:
--== no BACKTRACE for your platform ==--
Comment 2 echoxxzz 2022-10-21 01:18:35 UTC
If I rebuild amule with debug enabled amuled gives a bit more info before it eventually quits:

./src/common/selectdispatcher.cpp(204): assert "Assert failure" failed in ProcessSets(): NULL handler in wxSelectDispatcher?
Collecting stack trace information, please wait...

Call stack:
[00] 0x800ce7e02
[01] 0x800ce82a3
[02] 0x800ceb0d1
[03] 0x800ceb011
[04] 0x800c45ea9
[05] 0x800c45b6b
[06] 0x800c10506
[07] 0x800c79df1
Assertion failed: ./src/common/selectdispatcher.cpp:ProcessSets:204: Assertion 'Assert failure' failed. NULL handler in wxSelectDispatcher?
Backtrace follows:
--== no BACKTRACE for your platform ==--


I get a lot of these (or very similar) message from wxSelectDispatcher before amuled quits.
Comment 3 echoxxzz 2022-10-21 11:34:09 UTC
Rebuilt amule this time using wx28 and it ran a lot longer but eventually it also crashed:

A fatal error has occurred and aMule has crashed.
Please assist us in fixing this problem by posting the backtrace below in our
'aMule Crashes' forum and include as much information as possible regarding the
circumstances of this crash. The forum is located here:
    http://forum.amule.org/index.php?board=67.0
If possible, please try to generate a real backtrace of this crash:
    http://wiki.amule.org/wiki/Backtraces

----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMuleD 2.3.3 compiled with wxBase(GTK2) v2.8.12 (Debugging)
Running on: FreeBSD 13.1-RELEASE-p2 amd64

--== no BACKTRACE for your platform ==--
Comment 4 echoxxzz 2022-10-21 11:35:06 UTC
I rebuild this time using wx28 and it does a lot longer but it also crashes with the following error:

A fatal error has occurred and aMule has crashed.
Please assist us in fixing this problem by posting the backtrace below in our
'aMule Crashes' forum and include as much information as possible regarding the
circumstances of this crash. The forum is located here:
    http://forum.amule.org/index.php?board=67.0
If possible, please try to generate a real backtrace of this crash:
    http://wiki.amule.org/wiki/Backtraces

----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMuleD 2.3.3 compiled with wxBase(GTK2) v2.8.12 (Debugging)
Running on: FreeBSD 13.1-RELEASE-p2 amd64

--== no BACKTRACE for your platform ==--
Comment 5 Rene Ladan freebsd_committer freebsd_triage 2022-12-05 12:04:56 UTC
Maintainer reset.
Comment 6 Robert Clausecker freebsd_committer freebsd_triage 2023-04-19 12:37:23 UTC
See also bug #270916.
Comment 7 Nuno Teixeira freebsd_committer freebsd_triage 2024-04-15 19:28:18 UTC
This issue was fixed in https://cgit.freebsd.org/ports/commit/?id=4baf754027807e1ad7966055d40a4c4eb75a5717

Closing PR.