Andreas Schwab schwab@suse.de
Thu Mar 13 12:45:00 GMT 2003

• Previous message (by thread): section .init_array not working on ppc32
• Next message (by thread): section .init_array not working on ppc32
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Alan Modra <amodra@bigpond.net.au> writes:

|> On Thu, Mar 13, 2003 at 11:01:00AM +0100, Olaf Hering wrote:
|> > I'm not sure if that is a binutils or gcc bug, testcase is from glibc
|> > configure:
|> > 
|> > nectarine:~# gcc -o conftest conftest.c  -static -nostartfiles -nostdlib
|> > nectarine:~# ./conftest
|> > Segmentation fault
|> > nectarine:~# cat conftest.c
|> > int _start (void) { return 0; }
|> > int __start (void) { return 0; }
|> > int foo (void) { return 1; }
|> > int (*fp) (void) __attribute__ ((section (".init_array"))) = foo;
|> 
|> It's a glibc configure bug.  You can make this obvious by reducing
|> your conftest.c to just the first line, when the testcase compiles
|> and links to just

You are not supposed to execute this program.  It is only compiled to
look for existance of init_array support from the compiler.

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

---

• Previous message (by thread): section .init_array not working on ppc32
• Next message (by thread): section .init_array not working on ppc32
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Binutils mailing list