mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: abelbg@m2grp.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Elf loader crash while zero-filling .bss
Date: Fri, 08 Feb 2008 17:38:33 +0100	[thread overview]
Message-ID: <jefxw3pfna.fsf@sykes.suse.de> (raw)
In-Reply-To: <15577be70802080814j1bb21b30r6f8a82e35aa8dc07@mail.gmail.com> (Abel Bernabeu's message of "Fri\, 8 Feb 2008 17\:14\:50 +0100")

"Abel Bernabeu" <abelbg@m2grp.com> writes:

> The offset of some sections fall in the middle of the .bss section. In
> instance, look at the sections 12 (.comment) and 13 (.ARM.atributes).
> Both sections are overlapping with 11 (.bss):
>
> [11] .bss                 NOBITS       0001143c 00143c 000048  0 WA     0   0  4
> [12] .comment             PROGBITS     00000000 00143c 000094  0        0   0  1
> [13] .ARM.attributes      SHT_LOPROC+3 00000000 0014d0 000010  0        0   0  1
> [14] .shstrtab            STRTAB       00000000 0014e0 00007b  0        0   0  1
> [15] .symtab              SYMTAB       00000000 001804 000c70 16       16  92  4
> [16] .strtab              STRTAB       00000000 002474 000840  0        0   0  1
>
> Is this fact meaningful??

The fifth column is the file offset.  Since the .bss section does not
occupy any file space the other sections can be put directly behind it
in the file.

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."

  reply	other threads:[~2008-02-08 16:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 11:09 Abel Bernabeu
2008-01-31 15:38 ` Abel Bernabeu
2008-02-08 16:14   ` Abel Bernabeu
2008-02-08 16:38     ` Andreas Schwab [this message]
     [not found]       ` <15577be70802080954w6796bed1mbdf5fdc52e0cb2bf@mail.gmail.com>
2008-02-08 18:05         ` Fwd: " Abel Bernabeu

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=jefxw3pfna.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=abelbg@m2grp.com \
    --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®