lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 02 May 2009 01:10:18 +0200
From:	Andreas Schwab <schwab@...ux-m68k.org>
To:	"H. Peter Anvin" <hpa@...ux.intel.com>
Cc:	LKML <linux-kernel@...r.kernel.org>, linux-arch@...r.kernel.org,
	Sam Ravnborg <sam@...nborg.org>
Subject: Re: "N" symbols and System.map

"H. Peter Anvin" <hpa@...ux.intel.com> writes:

> right now, we filter out symbols that nm tag N, meaning "debugging
> symbols", from System.map.  However, at least on x86, the linker-generated
> symbol _end is tagged N, and in fact is the only N in the entire image.
>
> Are there other architectures which would suffer if N were included in
> System.map, or would that be a reasonable thing to do?

There should not be any N symbols unless you are using stabs debugging.

Andreas.

-- 
Andreas Schwab, schwab@...ux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ