public inbox for
 help / color / mirror / Atom feed
From: Michael Nonweiler <>
To: Ian Lance Taylor <>
Subject: Re: ELF STT_SECTION symbol for .comment section
Date: Fri, 12 Feb 1999 09:51:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

In summary, I'm writing to agree with you.

Thank you for your reply.

More detailed comments follow...

I wrote:
>   The problem is caused by the function elf_map_symbols in bfd/elf.c
>   generating an unnamed section symbol for the ".comment" section of an
>   object file.  This upsets my linker because it expects to map all symbols
>   to image locations, and the ".comment" section of the object file is not
>   part of the image.

When I say image locations here I really mean any valid location of the
linker's output file, debugging information included.

At 12:17 11/02/99 -0500, Ian Lance Taylor wrote:
>That expectation seems like a bug.  In fact, since some types of
>debugging informations have references between debugging sections,
>which require symbols in the debugging sections, I don't see how this
>can work in practice.

Yes.  For example, this is an issue if you instruct the linker to remove
debugging sections...

(rest snipped)

We intend to make our linker deal with this.



      reply	other threads:[~1999-02-12  9:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-11  4:12 Michael Nonweiler
1999-02-11  9:17 ` Ian Lance Taylor
1999-02-12  9:51   ` Michael Nonweiler [this message]

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:

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

  git send-email \ \ \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).