You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When amule runs, and the system clock does has a bigger time shift (at least to the future), amule crashes.
Those timeshifts happen e.g. already if the system is at sleep/ suspend to disk, but can also happen due to timezone change/ daylight saving time change.
So this scenario is a normal use case scenario.
Details:
When I start amule, and then suspend to disk for ~30 minutes, and then wake up the machine again, it crashes with a segmentation fault.
I have compiled aMule from this git repository with debugging information, checkout on 2024-11-26, git commit hash 2a307a3.
I also have compiled wxWidgets gtk3 with debugging symbols.
I run amule in GDB.
On the crash, I get the following terminal output:
When I then continue the execution, I get the following to the terminal (the backtrace now seems to be generated by aMule or wxWidgets, not by GDB):
--------------------------------------------------------------------------------
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: aMule GIT compiled with wxGTK2 v3.2.6 and Boost 1.86 (Debugging) (Snapshot: rev. 2.3.3-51-g2a307a3bd)
Running on: Linux 6.11.10-xanmod-customconfig-clang x86_64
[2] ?? in /usr/lib/libwx_baseu-3.2.so.0[0x7ffff6da2deb]
[3] ?? in /usr/lib/libc.so.6[0x7ffff664eb80]
[4] ?? in /usr/bin/amule[0x555555986e92]
[5] ?? in /usr/bin/amule[0x555555986f47]
[6] ?? in /usr/bin/amule[0x555555987548]
[7] ?? in /usr/bin/amule[0x555555990389]
[8] ?? in /usr/bin/amule[0x5555559903ba]
[9] ?? in /usr/bin/amule[0x555555990417]
[10] ?? in /usr/bin/amule[0x555555990535]
[11] ?? in /usr/bin/amule[0x555555990597]
[12] ?? in /usr/bin/amule[0x555555990692]
[13] ?? in /usr/bin/amule[0x555555990815]
[14] ?? in /usr/bin/amule[0x5555559908c6]
[15] ?? in /usr/bin/amule[0x555555977183]
[16] ?? in /usr/bin/amule[0x555555990607]
[17] ?? in /usr/bin/amule[0x555555990692]
[18] ?? in /usr/bin/amule[0x5555559906ba]
[19] ?? in /usr/bin/amule[0x5555559907a2]
[20] ?? in /usr/bin/amule[0x55555597763d]
[21] ?? in /usr/bin/amule[0x555555977f0c]
[22] ?? in /usr/bin/amule[0x55555597bac0]
[23] ?? in /usr/bin/amule[0x555555981cc8]
[24] wxThreadInternal::PthreadStart(wxThread*) in /usr/lib/libwx_baseu-3.2.so.0[0x7ffff6da1367]
[25] ?? in /usr/lib/libwx_baseu-3.2.so.0[0x7ffff6da1914]
[26] ?? in /usr/lib/libc.so.6[0x7ffff66a2eaa]
[27] ?? in /usr/lib/libc.so.6[0x7ffff672417c]
--------------------------------------------------------------------------------
Thread 9 "amule" received signal SIGABRT, Aborted.
__pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
And I am back in the GDB shell, where I can get another backtrace:
(This is a copy of this issue on bugs.amule.org. Since the git repository here is (aiming to be) active for further development of aMule, I report it now here, too, in an updated version.
The issue still persists.)
When
amule
runs, and the system clock does has a bigger time shift (at least to the future),amule
crashes.Those timeshifts happen e.g. already if the system is at sleep/ suspend to disk, but can also happen due to timezone change/ daylight saving time change.
So this scenario is a normal use case scenario.
Details:
When I start
amule
, and then suspend to disk for ~30 minutes, and then wake up the machine again, it crashes with a segmentation fault.I have compiled aMule from this git repository with debugging information, checkout on 2024-11-26, git commit hash 2a307a3.
I also have compiled wxWidgets gtk3 with debugging symbols.
I run
amule
in GDB.On the crash, I get the following terminal output:
Then, i am thrown to the GDB shell, and a backtrace gives:
When I then continue the execution, I get the following to the terminal (the backtrace now seems to be generated by aMule or wxWidgets, not by GDB):
And I am back in the GDB shell, where I can get another backtrace:
Continuing then leads to abortion of
amule
:Attached: Complete terminal output of the run of
gdb amule
: Combined stdout, stderr and GDB session:amule_gdb-session.log
.Regards!
The text was updated successfully, but these errors were encountered: