[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090501232149.GA28888@uranus.ravnborg.org>
Date: Sat, 2 May 2009 01:21:49 +0200
From: Sam Ravnborg <sam@...nborg.org>
To: Andreas Schwab <schwab@...ux-m68k.org>
Cc: "H. Peter Anvin" <hpa@...ux.intel.com>,
LKML <linux-kernel@...r.kernel.org>, linux-arch@...r.kernel.org
Subject: Re: "N" symbols and System.map
On Sat, May 02, 2009 at 01:10:18AM +0200, Andreas Schwab wrote:
> "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.
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
--
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