mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: discarded `.exit.text' debugging?
Date: Tue, 21 Oct 2008 00:01:39 +0200	[thread overview]
Message-ID: <je3airq62k.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0810202207140.23258@anakin> (Geert Uytterhoeven's message of "Mon, 20 Oct 2008 22:09:11 +0200 (CEST)")

Geert Uytterhoeven <geert@linux-m68k.org> writes:

> Last night I got these in my build logs:
>
> | `.exit.text' referenced in section `.init.text' of drivers/built-in.o: defined in discarded section `.exit.text' of drivers/built-in.o
> | `.exit.text' referenced in section `.data' of drivers/built-in.o: defined in discarded section `.exit.text' of drivers/built-in.o
>
> i.e. not much context. Is there an easy way to find out who's the
> offender?

You could try giving each .exit.text section a unique name per object
file (so that "ld -r" does not merge them) and modify EXIT_TEXT to
collect all those sections during the final link.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  parent reply	other threads:[~2008-10-20 22:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20 20:09 Geert Uytterhoeven
2008-10-20 20:28 ` linux-os (Dick Johnson)
2008-10-20 22:01 ` Andreas Schwab [this message]
2008-10-26 18:32 ` Geert Uytterhoeven

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=je3airq62k.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®