Print

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

[Pitxyoki]

Operating System: Debian Lenny

Code: [Select]

$ uname -a
Linux C-1 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686 GNU/Linux
aMule version:

Code: [Select]

$ dpkg -l | grep mule
ii  amule-common                           2.2.1-1                    common files for the rest of aMule packages
ii  amule-daemon                           2.2.1-1                    non-graphic version of aMule, a client for the eD2k and Kad netw

I usually have amuled running on my server computer and I connect to it through amulegui or amuleweb.
The logfile output shows that it was connected to some server. Apparently it crashed when noone was touching it.
Notice that the last amulegui access made to it was yesterday and today at 7AM it was still running, as it received those messages from the server.
~/.aMule/logfile:

Code: [Select]

2009-03-02 22:26:39: ExternalConn.cpp(218): New external connection accepted
2009-03-02 22:26:39: ExternalConn.cpp(252): Connecting client: amule-remote 0x0001
2009-03-02 22:26:39: ExternalConn.cpp(307): Access granted.
2009-03-02 22:27:35: ExternalConn.cpp(117): External connection closed.
2009-03-02 23:06:49: ServerMessage: .
2009-03-02 23:06:49: ServerMessage: Test Usenet downloads at full DSL-Speed for 2 weeks free and get 150GB http://test.eDonkey.to
2009-03-03 07:07:21: ServerMessage: .
2009-03-03 07:07:21: ServerMessage: Test Usenet downloads at full DSL-Speed for 2 weeks free and get 150GB http://test.eDonkey.to
tail: .aMule/logfile: file truncated

Here is the output from amuled seen on stdout:

Code: [Select]

(...)
Server hostname notified
Unknown port receiving an UDP packet! Ignoring

--------------------------------------------------------------------------------
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://www.amule.org/wiki/index.php/Backtraces

----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMuled 2.2.1 using wxGTK2 v2.8.7
Running on: Linux 2.6.26-1-686 i686

[2] wxAppTraitsBase::GetDesktopEnvironment() const in amuled [0x8070f41]
[3] wxFatalSignalHandler in /usr/lib/libwx_baseu-2.8.so.0[0xb7aaf1e6]
[4] ?? in [0xb7f91400]
[5] wxStringBase::~wxStringBase() in amuled [0x81a6c18]
[6] wxFFile::~wxFFile() in amuled [0x81c35c2]
[7] wxMutexLocker::~wxMutexLocker() in amuled [0x8112e09]
[8] CryptoPP::IteratedHash<unsigned int, CryptoPP::EnumToType<CryptoPP::ByteOrder, 0>, 64u, CryptoPP::HashTransformation>::~IteratedHash() in amuled [0x811f971]
[9] wxMutexLocker::~wxMutexLocker() in amuled [0x8116497]
[10] CryptoPP::AlgorithmImpl<CryptoPP::TF_SignerBase, CryptoPP::TF_SS<CryptoPP::PKCS1v15, CryptoPP::SHA1, CryptoPP::RSA, int> >::AlgorithmName() const in amuled [0x80a5aa1]
[11] wxMutexLocker::~wxMutexLocker() in amuled [0x80e5c8b]
[12] CryptoPP::AlgorithmImpl<CryptoPP::TF_SignerBase, CryptoPP::TF_SS<CryptoPP::PKCS1v15, CryptoPP::SHA1, CryptoPP::RSA, int> >::AlgorithmName() const in amuled [0x80a4a89]
[13] wxAppConsole::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) const in /usr/lib/libwx_baseu-2.8.so.0[0xb7a0d7f1]
[14] wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) in /usr/lib/libwx_baseu-2.8.so.0[0xb7aaa9ca]
[15] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) in /usr/lib/libwx_baseu-2.8.so.0[0xb7aabbb4]
[16] wxEvtHandler::ProcessEvent(wxEvent&) in /usr/lib/libwx_baseu-2.8.so.0[0xb7aabcbb]
[17] wxEvtHandler::ProcessPendingEvents() in /usr/lib/libwx_baseu-2.8.so.0[0xb7aaae30]
[18] wxAppConsole::ProcessPendingEvents() in /usr/lib/libwx_baseu-2.8.so.0[0xb7a0db51]
[19] ?? in amuled [0x806e189]
[20] wxEntry(int&, wchar_t**) in /usr/lib/libwx_baseu-2.8.so.0[0xb7a4702a]
[21] wxEntry(int&, char**) in /usr/lib/libwx_baseu-2.8.so.0[0xb7a47227]
[22] ?? in amuled [0x806d800]
[23] __libc_start_main in /lib/i686/cmov/libc.so.6[0xb7759455]
[24] CryptoPP::Filter::Flush(bool, int, bool) in amuled[0x806c8b1]


--------------------------------------------------------------------------------
Aborted


By the way, as an off-topic, I've been submitting bug reports to the Debian bug tracking system but I never received any input from there. Should I submit the reports to this forum or should I keep mailing them to Debian? They were mainly improvement suggestions, so they should not be specific to the Debian distribution, but they always recommend we submit all bugs to them... 

[wuischke]

Please update to wxWidgets 2.8.9 and aMule 2.2.3, we cannot support older versions.

You can send bug reports / improvements regarding aMule to us, we encourage it even! But we won't be able to implement everything, unfortunately.

[Stu Redman]

You can send bug reports / improvements regarding aMule to us

You can send bug reports / improvements regarding aMule only to us.
If debian started shipping modified amule version we would have to stop supporting debian users. Remember what they did to OpenSSL (shudder).

[Pitxyoki]

Well, I'm not going to start one more flaming discussion about the Debian procedures for bug reporting.
I don't even know much about it, but I think I see their point: once they do some modifications to some packages they provide, they are the ones who should be bothered if the packages give problems.


Some projects actually don't support their Debian users and prefer to keep contact only with the Debian package maintainer. This seems to work fine when there are significant changes made to the packages and the maintainer is active and willing to cooperate.

Anyway, I've scrolled through the debian diff file and the only changes that seem to be made to the amule source seem to be relative to the location of some files on the filesystem, the addition of a debian changelog, a debian readme and some changes to provide the autostart of the amule daemon with the init system.
I'm not very experienced with diff files, but these don't seem to me like big changes, but just adaptations to make the program more compliant to the Debian standards.

I'll send you two of the suggestions I sent to Debian after I test the most recent version that I'll install here "soon". 

[Stu Redman]

once they do some modifications to some packages they provide, they are the ones who should be bothered if the packages give problems.

Exactly my point - if someone mods our app he has to do all the support for the mod (like adundanza or whatever it's called), and questions here regarding the mod go straight to the bin. 
Anyway, debian doesn't count as mod, so this has no practical relevance.

I'll send you two of the suggestions I sent to Debian after I test the most recent version that I'll install here "soon". 

Go ahead (use the feature board please).