<a href="http://g.adspeed.net/ad.php?do=clk&zid=14678&wd=728&ht=90&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=14678&wd=728&ht=90&pair=as" alt="i" width="728" height="90"/></a>

Nmap Security Scanner

Docs
Security Lists

Full Disclosure

More
Security Tools

Packet crafters

More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:

edgeos

Nmap Development: Re: [Bug?] memory could not be read in liblua/ldo.c resume_error

Re: [Bug?] memory could not be read in liblua/ldo.c resume_error

From: jah <jah_at_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.
>
> Thanks,
It looks like you got it, it doesn't happen any longer.

Cheers,

jah

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org
Received on Jun 21 2008

This message: [ Message body ]
Next message: jah: "Re: [PATCH] http.lua updated in line with stdnse.make_buffer()"
Previous message: jah: "Re: [PATCH] lil' mistake in stdnse.lua"
In reply to: Patrick Donnelly: "Re: [Bug?] memory could not be read in liblua/ldo.c resume_error"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]

[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]

edgeos