From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sam Ravnborg Subject: Re: "N" symbols and System.map Date: Sat, 2 May 2009 01:21:49 +0200 Message-ID: <20090501232149.GA28888@uranus.ravnborg.org> References: <49FB7692.2000508@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from pfepb.post.tele.dk ([195.41.46.236]:48995 "EHLO pfepb.post.tele.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753549AbZEAXTk (ORCPT ); Fri, 1 May 2009 19:19:40 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-arch-owner@vger.kernel.org List-ID: To: Andreas Schwab Cc: "H. Peter Anvin" , LKML , linux-arch@vger.kernel.org On Sat, May 02, 2009 at 01:10:18AM +0200, Andreas Schwab wrote: > "H. Peter Anvin" 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. We have in vmlinux: .end : AT(ADDR(.end) - LOAD_OFFSET) { _end = .; } And I see: c1834000 N _end This is the _only_ 'N' symbol in my vmlinux. Sam