Your message dated Thu, 20 Nov 2014 09:19:54 +0100 with message-id <[email protected]> and subject line Re: Bug#770223: nmap: Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_vers... has caused the Debian Bug report #770223, regarding nmap: Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_vers... to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 770223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770223 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: nmap Version: 6.47-3 Severity: important Dear Maintainer, Thanks for maintaining Debian's nmap package. I like using it to report the IP addresses assigned on my private network. My understanding is this can be done with $ nmap -sP 192.168.1.0/24 and $ nmap -sn 192.168.1.0/24 I expected nmap to return something like Host 192.168.0.1 is up (0.00035s latency). MAC Address: BC:AE:C5:C3:16:93 (Unknown) Host 192.168.0.2 is up (0.0038s latency). MAC Address: 74:44:01:40:57:FB (Unknown) Host 192.168.0.5 is up. Host nas03 (192.168.0.12) is up (0.0091s latency). MAC Address: 00:11:32:11:15:FC (Spleenology Uncorporated) Nmap done: 256 IP addresses (4 hosts up) scanned in 2.80 second However, I just tried both ways, and nmap complained with Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions: Assertion `needed != ((void *)0)' failed! I get the same error with $ ldd $(which nmap) I have not yet found a way to work around the bug. It looks like bug 70503. Ben Collins evidently thought in 2002 that this was a bug in executables, and if they had a DT_NEEDED entry that was empty, then they were linked incorrectly. For what it's worth, I'm using unstable's latest /usr/bin/ldd from the 2.19-13 version of the libc-bin package. Have you recently changed how nmap is linked or compiled? Thanks, Kingsley -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages nmap depends on: ii libc6 2.19-13 ii libgcc1 1:4.9.1-4 ii liblinear1 1.8+dfsg-1 ii liblua5.2-0 5.2.3-1 ii libpcap0.8 1.4.0-2 ii libpcre3 1:8.31-2 ii libssl1.0.0 1.0.1j-1 ii libstdc++6 4.9.1-4 Versions of packages nmap recommends: ii ndiff 6.47-1 nmap suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---* Kingsley G. Morse Jr.: > I'm happy to report that upgrading just the > package named "libpcre3" from version 1:8.31-2 to > 1:8.35-3.2 seems to have solved the problem. Nice, so I can close this bug. > What would you think of changing nmap to depend on > version 8.35-3.2 or greater of libpcre3? Not really. We don't know the list of libpcre3 versions that broke nmap (and possibly other programs). Within a year (more likely a month), I would forget why I added the versioned dependency. And the libpcre3 dependency, like all library dependencies is generated automatically using dpkg-shlibdeps anyway. Cheers, -Hilko
--- End Message ---
