On 25/05/20(Mon) 10:14, Claudio Jeker wrote: > [...] > One approach to fix this is to ensure that the event functions are > exclusivly used in the main event thread but as usual it is easy to > introduce bugs again.
This is a common issue with multi-threaded applications using non thread-safe libraries. Isn't it possible to have a mechanism to add a warning or trigger an abort(3) if a thread other than the main event thread calls a libevent function?
