public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-arch@vger.kernel.org
Subject: Re: "N" symbols and System.map
Date: Fri, 01 May 2009 17:00:39 -0700	[thread overview]
Message-ID: <49FB8D27.3000305@linux.intel.com> (raw)
In-Reply-To: <20090501232149.GA28888@uranus.ravnborg.org>

Sam Ravnborg wrote:
> On Sat, May 02, 2009 at 01:10:18AM +0200, Andreas Schwab wrote:
>> "H. Peter Anvin" <hpa@linux.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.
> 

Yup, this is what happens.  I don't know why the linker does this, and 
if there is a way around it.

	-hpa

  reply	other threads:[~2009-05-02  0:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-01 22:24 "N" symbols and System.map H. Peter Anvin
2009-05-01 22:39 ` Luck, Tony
2009-05-01 23:10 ` Andreas Schwab
2009-05-01 23:21   ` Sam Ravnborg
2009-05-02  0:00     ` H. Peter Anvin [this message]
2009-05-04 19:33       ` Sam Ravnborg
2009-05-04 19:33         ` Sam Ravnborg
2009-05-04 21:19         ` Andreas Schwab
2009-05-04 21:26           ` H. Peter Anvin
2009-05-04 21:39           ` Luck, Tony
2009-06-05 22:26 ` Sam Ravnborg
2009-06-05 22:28   ` H. Peter Anvin
2009-06-05 22:37     ` Sam Ravnborg
2009-06-05 22:49       ` H. Peter Anvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49FB8D27.3000305@linux.intel.com \
    --to=hpa@linux.intel.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=schwab@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox