[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
nmap-2.54b{25,33} SIGSEGV on sparc64-3.1
- To: ports_(_at_)_openbsd_(_dot_)_org
- Subject: nmap-2.54b{25,33} SIGSEGV on sparc64-3.1
- From: Gregory Steuck <greg_(_at_)_nest_(_dot_)_cx>
- Date: Mon, 20 May 2002 16:20:54 -0700
- Cc: Brian Caswell <bmc_(_at_)_openbsd_(_dot_)_org>
[greg_(_at_)_tidy nmap]$ sudo nmap -sU localhost
Starting nmap V. 2.54BETA25 ( www.insecure.org/nmap/ )
caught SIGSEGV signal, cleaning up
... when it tries to ping the scanned system. The root cause of SEGV is
nmap compiling with it's own pcap.h and then linking with the system
libpcap.so. Just compare the size of pcap_pkthdr inside libpcap (16) and
in nmap (24).
If I do a barbarian modification to the port's Makefile (below), I get a
working nmap. Could somebody do it cleaner?
Thanks
Greg
P.S. IMO nmap code is ugly.
Index: Makefile
===================================================================
RCS file: /cvs/ports/net/nmap/Makefile,v
retrieving revision 1.40
diff -u -r1.40 Makefile
--- Makefile 2002/04/28 20:36:02 1.40
+++ Makefile 2002/05/20 23:18:01
@@ -19,8 +19,9 @@
PERMIT_DISTFILES_FTP= Yes
CONFIGURE_STYLE= gnu dest
-MODGNU_CONFIG_GUESS_DIRS= ${WRKSRC} ${WRKSRC}/nbase ${WRKSRC}/libpcap-possiblymodified
+MODGNU_CONFIG_GUESS_DIRS= ${WRKSRC} ${WRKSRC}/nbase
+CONFIGURE_ARGS= --with-libpcap=/usr
FLAVORS= no_x11
FLAVOR?=
Visit your host, monkey.org