PenTest/nmap
1
0
Fork 0
mirror of https://github.com/nmap/nmap.git synced 2026-01-01 20:39:02 +00:00
Code Issues Projects Releases Wiki Activity

Temporarily increase the size of the traceroute output table by 1 until

Browse Source 
I can find the bug that causes too many rows to be printed in debugging
mode in some cases. I get an assertion failure when running
	nmap scanme.nmap.org/26 --top-ports 10 --traceroute -n -d
With this change, the bug manifests itself as some peculiar output:

4   --        66.54.149.185
5   --        63.211.250.17
5   39.17 ms  63.211.250.17
6   47.12 ms  4.68.107.190
7   39.72 ms  4.69.132.37

(Note the doubled 5 with the same IP address.)

10  --        207.88.13.122
11  --        207.88.12.46
12  --        207.88.12.61
13  --        65.106.1.57
13  100.77 ms 65.106.1.65
14  91.75 ms  65.106.5.162

(Note the doubled 13 with a different IP address.)

4   --       66.54.149.185
5   --       63.211.250.17
5   ...
6   39.32 ms 4.68.107.190

(Note the doubled 5 with a timeout.)
This commit is contained in:
david
2009-08-20 18:22:31 +00:00
parent 09ba9eda1f
commit c3b5c08941
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
traceroute.cc
View File

@@ -901,7 +901,9 @@ Traceroute::outputTarget(Target * t) {
this->outputXMLTrace(tg);
/* table headers */
Tbl = new NmapOutputTable(tg->hopDistance+1, 3);
/* This should be tg->hopDistance + 1, but there is a bug that sometimes
causes an extra row to be printed. */
Tbl = new NmapOutputTable(tg->hopDistance+2, 3);
Tbl->addItem(row_count, HOP_COL, false, "HOP", 3);
Tbl->addItem(row_count, RTT_COL, false, "RTT", 3);
Tbl->addItem(row_count, HOST_COL, false, "ADDRESS", 7);