Finally, a lead what could still cause my development version of #swad to crash!
Ok, this looks really weird, the failed assertion at the bottom means a thread ends up fiddling with an event that's owned by a different thread.
But hey, at least now I have stacktraces of what's happening.
Just wow. This code is so *obviously* wrong, no idea what I was thinking writing that. The PSC_IpAddr_string() method returns a pointer inside the IpAddr object, so destroying it in the next line is really bullshit 🙈
Unfortunately, this doesn't explain the failed assertion at all. Guess I'm hunting more than just one bug ... 😔
Yep, there's a second bug. #clang #thread #sanitizer had nothing to complain, and the output from #assert doesn't help much. So, first step: "pimp your assert" 😂 --- #FreeBSD, like some other systems, provides functions to collect and print rudimentary stacktraces, use these if available:
https://github.com/Zirias/poser/commit/c45dd56312dd05b6bf02a27bf9e39eb31331f05a
Now I got closer, see screenshot. That's enough to understand, the issue is with the global event firing when a #child #process exits, this was used from multiple threads. Ok, it obviously doesn't work that way, so, back to the drawing board regarding my handling for child processes... 🤔
Next #swad release: Soon, so I hope 🙈
Fixed *that* issue by making sure each instance of the Process class has an owning thread, but forks the child on the main thread and receives exit events from there, delegating that info back to the owing thread. Seems to work.
Now, I can still make #swad crash. But no matter what I tried so far, as soon as I build it with both #debugging symbols and the #thread #sanitizer, I just can't reproduce a crash.
Now what? 😞🤷
Felix Palmen 
