New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

openbsd timing.cc coredump #472

Closed
jungle-boogie opened this Issue Jul 23, 2016 · 4 comments

Comments

Projects
None yet
2 participants
@jungle-boogie

jungle-boogie commented Jul 23, 2016

OpenBSD current on nmap commit 6d8b899 results in a coredump when doing the following:

 $ nmap -sT 192.168.0.8  

Starting Nmap 7.25SVN ( https://nmap.org ) at 2016-07-23 11:56 PDT
assertion "diff <= interval" failed: file "timing.cc", line 440, function "update"
Abort trap (core dumped)

nmap/timing.cc

Line 440 in 799048e

assert(diff <= interval);

@dmiller-nmap

This comment has been minimized.

dmiller-nmap commented Aug 30, 2016

Fixed in d4f698b. We left in an error statement so we can figure out why this is happening in the first place, but you're right that it shouldn't cause a complete crash. Thanks!

@jungle-boogie

This comment has been minimized.

jungle-boogie commented Sep 9, 2016

worked one time:

$ nmap -sT 192.168.0.1

Starting Nmap 7.25SVN ( https://nmap.org ) at 2016-09-09 16:02 PDT
Nmap scan report for 192.168.0.1
Host is up (0.0093s latency).
Not shown: 995 filtered ports
PORT     STATE  SERVICE
22/tcp   closed ssh
23/tcp   closed telnet
80/tcp   open   http
443/tcp  open   https
1900/tcp closed upnp

Nmap done: 1 IP address (1 host up) scanned in 5.25 seconds

then core dump again:

$ nmap -sT 192.168.0.1

Starting Nmap 7.25SVN ( https://nmap.org ) at 2016-09-09 16:03 PDT
assertion "diff <= interval" failed: file "timing.cc", line 440, function "update"
Abort trap (core dumped)

nmap-bot pushed a commit that referenced this issue Oct 16, 2016

@dmiller-nmap

This comment has been minimized.

dmiller-nmap commented Oct 19, 2016

@jungle-boogie Apparently we fixed the wrong thing (which was also a reported bug), but this issue has actually been fixed in c104245 and 6352cb1.

@jungle-boogie

This comment has been minimized.

jungle-boogie commented Oct 19, 2016

@dmiller-nmap,

YES! this actually scans without a crash!!

nmap -sT 192.168.0.1

Starting Nmap 7.30SVN ( https://nmap.org ) at 2016-10-19 08:26 PDT
Nmap scan report for 192.168.0.1
Host is up (0.011s latency).
Not shown: 995 filtered ports
PORT     STATE  SERVICE
22/tcp   closed ssh
23/tcp   closed telnet
80/tcp   open   http
443/tcp  open   https
1900/tcp closed upnp

Nmap done: 1 IP address (1 host up) scanned in 5.35 seconds
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment