Nmap Development mailing list archives
Re: time_t changes in OpenBSD-current
From: David Fifield <david () bamsoftware com>
Date: Mon, 6 Jan 2014 19:35:42 -0800
On Sat, Jan 04, 2014 at 05:18:41PM +0100, Giovanni Bechis wrote:
in september OpenBSD changed time_t to long long on all platforms, this change broke nmap on 32 bits platforms. IMHO the main reason is that timing.cc class stores data in a double and some precision is lost. The following patch seems to fix the problem, maybe a bit more work is needed.
Thanks for this patch. Do we need to also add a cast to (long long) so it will work on other platforms where time_t is long or unsigned long? David _______________________________________________ Sent through the dev mailing list http://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- time_t changes in OpenBSD-current Giovanni Bechis (Jan 04)
- Re: time_t changes in OpenBSD-current David Fifield (Jan 06)
- Re: time_t changes in OpenBSD-current Daniel Miller (Jan 06)
- Re: time_t changes in OpenBSD-current David Fifield (Jan 07)
- Re: time_t changes in OpenBSD-current Giovanni Bechis (Jan 09)
- Re: time_t changes in OpenBSD-current Daniel Miller (Jan 06)
- Re: time_t changes in OpenBSD-current Giovanni Bechis (Jan 10)
- Re: time_t changes in OpenBSD-current David Fifield (Jan 06)