On 06/05/2015 08:15 PM, Jan Mareš wrote: > Concerning the second panic, I am convinced that threads can't be used > as execution containers. There is a race condition causing memory > corruption in the process. How resistant udebug is to corrupted memory > of the process I don't know, but first I would try to remove the race > condition.
I am not that convinced about this one. Udebug is in the kernel and here we are dealing with uspace stuff. I can see a thread which is interrupted from futex_sleep() and so it executes thread_exit(), where it assumes that it has a go call (in the udebug parlance), but that's not the case, so the kernel panics. udebug should probably check for the go in this case, to behave gracefully. On the other hand, it is not clear, why taskdump (which is run on the crashing test) cannot finish its job in a timely manner. Jakub _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
