Nmap Development mailing list archives
Re: Error: vsnprintf returned -1 in log_vwrite
From: Fyodor <fyodor () insecure org>
Date: Sun, 15 Jul 2007 16:24:26 -0700
On Sun, Jul 15, 2007 at 04:18:26PM +0100, jah wrote:
Host 192.168.1.5 appears to be up ... good. Interesting ports on 192.168.1.5: vsnprintf returned -1 in log_vwrite -- bizarre. Quitting. QUITTING!
Thanks for the report. Linux vsnprintf returns the amount of space needed when the buffer passed in is too short. Nmap already has code to lengthen the buffer in that case. But Windows apparently just returns -1. I have just checked in a change to nmap-exp/soc07/nmap/output.cc which grows the buffer in that case. This should resolve it. But if you still see the problem in the latest SVN version or after the next release, please let us know. Cheers, -F _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Error: vsnprintf returned -1 in log_vwrite jah (Jul 15)
- Re: Error: vsnprintf returned -1 in log_vwrite Fyodor (Jul 15)
- Re: Error: vsnprintf returned -1 in log_vwrite jah (Jul 15)
- Re: Error: vsnprintf returned -1 in log_vwrite Fyodor (Jul 15)