RE: 2.11.1

["Ken Whaley" <ken at believe dot com>]

The following happens on alpha linux with gcc 2.95.2 and binutils 2.10.90
and glibc 2.1.3-21.
I'm not sure if this is a gcc or binutils issue, but since releases
are coming soon and this seems to be a pretty nasty problem, here it is:

file "mylib.c" with contents "int i;"
% gcc -o mylib.o mylib.c -c -fPIC -ggdb
% gcc -o mylib.so mylib.o -shared

file "main.c" with contents "extern int i; main() { i = 0; }"
% gcc -o main.o main.c -c
% gcc -o main main.o mylib.so
% ./main
Seg fault

Removing the "-ggdb" from the first compile line fixes the problem.
Doesn't happen on x86.

Ken


> -----Original Message-----
> From: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org]On Behalf Of
> Philip Blundell
> Sent: Tuesday, June 05, 2001 1:46 PM
> To: binutils@sources.redhat.com
> Cc: gcc@gcc.gnu.org
> Subject: 2.11.1
>
>
> It would be pretty bad form to allow GCC 3.0 to ship before the
> next release
> of binutils.  I'm tentatively planning to make a 2.11.1 release (from the
> branch, obviously) in a week's time.
>
> As ever, please test the branch on your favourite targets.  If
> anybody knows
> of outstanding issues that need to be addressed either in
> binutils 2.11.1 for
> its own sake, or because they are needed for GCC, speak up now.
>
> p.
>
>
>