Nmap Development mailing list archives
Re: nmap stack overflow in output subsystem
From: David Fifield <david () bamsoftware com>
Date: Tue, 3 Jul 2012 01:08:40 -0700
On Tue, Jul 03, 2012 at 12:39:03AM +0200, Henri Doreau wrote:
Small update: even though my previous patch fixes the symptoms it doesn't actually remove the call loop between fatal() and log_vwrite(). This second patch, attached, replaces the one I sent earlier. It calls abort() instead of fatal() on unknown event log types, which I think is OK in this case. Any thought?
Your patch looks right to me. It was my mistake in r29083. Your fix to log_vwrite is better than reverting that revision. David Fifield _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
Current thread:
- nmap stack overflow in output subsystem Henri Doreau (Jul 02)
- Re: nmap stack overflow in output subsystem Henri Doreau (Jul 02)
- Re: nmap stack overflow in output subsystem Ron (Jul 02)
- Re: nmap stack overflow in output subsystem David Fifield (Jul 03)
- Re: nmap stack overflow in output subsystem Henri Doreau (Jul 03)
- Re: nmap stack overflow in output subsystem Daniel Miller (Jul 03)
- Re: nmap stack overflow in output subsystem David Fifield (Jul 03)
- Re: nmap stack overflow in output subsystem Daniel Miller (Jul 03)
- Re: nmap stack overflow in output subsystem Henri Doreau (Jul 02)