Closed CaveNightingale closed 1 year ago
Please use a debugger like gdb to give a detailed backtrace. Also, providing more information about the os environment will help to solve this.
I haven't got any stacktrace because I am not able to reproduce this.
Device Info: Huawei CREF-16 Intel i5-12500H Ubuntu 22.10
---Original--- From: "Annie K Rarity @.> Date: Sun, Jan 29, 2023 11:31 AM To: @.>; Cc: @.**@.>; Subject: Re: [Andy-K-Sparklight/Ari] AlicornCH Crashed (Issue #30)
Please use a debugger like gdb to give a detailed backtrace. Also, providing more information about the os environment will help to solve this.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
It was fixed in f973452f5206cfc487ce8459ba7648a19f8a3364 on macOS. I will try to revert it on GNU.
It was fixed in f973452 on macOS. I will try to revert it on GNU.
I think you are talking about #28
It might likely to happen when there is memory overwriting executable segments. But possible similar crashes haven't been reported yet.
It didn't revert, whatever it exited normally, with sigint, or even using sigkill, for nearly hundreds of times in gdb. Fairly interesting. Info: Arch Linux AArch64
Since it's really hard to reproduce, I guess it was related to thread-safety in some way. I've found that you spawn tons of threads as worker, so I'm going to have a look there.
As there are no further reports, this issue is marked as closed.
Some further research is needed.