mailing list archives
Re: [Bug?] memory could not be read in liblua/ldo.c resume_error
From: jah <jah () zadkiel plus com>
Date: Sat, 21 Jun 2008 20:55:27 +0100
On 21/06/2008 19:54, Patrick Donnelly wrote:
I believe I've fixed this. I found a related bug (I couldn't reproduce
yours specifically). The problem was waiting2running was pushing
threads to the front of the running queue while mainloop was popping
the first running thread (assuming the thread that just yielded is at
the front). Please see if this still happens.
It looks like you got it, it doesn't happen any longer.
Sent through the nmap-dev mailing list
Archived at http://SecLists.Org