Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 9 Oct 2002 11:56:01 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 9 Oct 2002 11:56:01 -0400 Received: from ns.suse.de ([213.95.15.193]:16903 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id ; Wed, 9 Oct 2002 11:56:00 -0400 To: root@chaos.analogic.com Cc: "J.A. Magallon" , Linux kernel Subject: Re: Writable global section? References: X-Yow: Put FIVE DOZEN red GIRDLES in each CIRCULAR OPENING!! From: Andreas Schwab Date: Wed, 09 Oct 2002 18:01:42 +0200 In-Reply-To: ("Richard B. Johnson"'s message of "Wed, 9 Oct 2002 11:56:00 -0400 (EDT)") Message-ID: User-Agent: Gnus/5.090007 (Oort Gnus v0.07) Emacs/21.3.50 (ia64-suse-linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1104 Lines: 28 "Richard B. Johnson" 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." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/