From: Andreas Schwab <schwab@suse.de>
To: root@chaos.analogic.com
Cc: "J.A. Magallon" <jamagallon@able.es>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Writable global section?
Date: Wed, 09 Oct 2002 18:01:42 +0200 [thread overview]
Message-ID: <jed6qj1tzt.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.LNX.3.95.1021009114700.6928B-100000@chaos.analogic.com> ("Richard B. Johnson"'s message of "Wed, 9 Oct 2002 11:56:00 -0400 (EDT)")
"Richard B. Johnson" <root@chaos.analogic.com> writes:
|> Well, yes I found out.. This anomaly with the assembler.....
|>
|> .section .data
|> .global pars
|> .type pars,@object
|> .size pars,4
|> .align 4
|> pars: .long 0
|> .end
|>
|>
|> I accidentally left out .size, guess what? Even though I had an
|> offset recognized and a ".long", initialized to 0, there was no
|> space allocated and therefore the seg-fault. I would have seen
|> this, but the problem doesn't exist if the ".section" is ".bss",
|> the first section I was messing with. Go figure?
I think this problem only exists on platforms with COPY relocations.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2002-10-09 15:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.95.1021009090100.31255A-100000@chaos.analogic.com>
2002-10-09 13:08 ` Richard B. Johnson
2002-10-09 14:24 ` J.A. Magallon
2002-10-09 14:49 ` Richard B. Johnson
2002-10-09 15:06 ` Brian Gerst
2002-10-09 15:46 ` Richard B. Johnson
2002-10-09 15:06 ` Andreas Schwab
2002-10-09 15:56 ` Richard B. Johnson
2002-10-09 16:01 ` Andreas Schwab [this message]
2002-10-09 23:14 ` Jamie Lokier
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=jed6qj1tzt.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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®