On Fri, May 01, 2009 at 05:00:39PM -0700, H. Peter Anvin wrote:
> Sam Ravnborg wrote:
> >On Sat, May 02, 2009 at 01:10:18AM +0200, Andreas Schwab wrote:
> >>"H. Peter Anvin" <hpa@xxxxxxxxxxxxxxx> 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.
> >
>
> Yup, this is what happens. I don't know why the linker does this, and
> if there is a way around it.
Andreas - can you explain what is happning here?
I can include 'N' symbols in System.map - but I have not yet reached
a level of understanding that make me go and do it.
Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
