51514 – gcc-3.4.0 breaks SSP in glibc

Bug 51514 - gcc-3.4.0 breaks SSP in glibc

Summary: gcc-3.4.0 breaks SSP in glibc

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	x86 All

Importance:	High major (vote)
Assignee:	Gentoo Toolchain Maintainers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:	48528
	Show dependency tree

Reported:	2004-05-19 16:05 UTC by Tuan Van (RETIRED)
Modified:	2004-06-06 13:24 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Tuan Van (RETIRED) gentoo-dev

2004-05-19 16:05:46 UTC

$ firefox
No running windows found
/usr/lib/MozillaFirefox/firefox-bin: relocation error: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.4.0/libstdc++.so.6: symbol __guard, version GCC_3.0 not defined in file libgcc_s.so.1 with link time reference

# emerge info
Portage 2.0.50-r6 (default-x86-2004.0, gcc-3.4.0, glibc-2.3.3_pre20040420-r0, 2.6.5-gentoo-r1)
=================================================================
System uname: 2.6.5-gentoo-r1 i686 Intel(R) Pentium(R) 4 CPU 1.80GHz
Gentoo Base System version 1.4.14
ccache version 2.3 [disabled]
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=pentium4 -fomit-frame-pointer -pipe "
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"

Comment 1 George L. Emigh 2004-05-19 16:42:56 UTC

similar problem with gcc-3.4.0-r3 and mysql-4.0.20:

/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.0/libstdc++.so: undefined reference to `__guard@GCC_3.0' 
 /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.0/libstdc++.so: undefined reference to `__stack_smash_handler@GCC_3.0' 
 collect2: ld returned 1 exit status 
 make[2]: *** [mysqladmin] Error 1


George

Comment 2 Robert Moss (RETIRED) gentoo-dev

2004-05-19 17:56:55 UTC

I can also confirm this bug, looks like a pretty serious change hit somewhere with that CVS snapshot, lv.

Comment 3 Travis Tilley (RETIRED) gentoo-dev

2004-05-19 22:10:26 UTC

your gcc 3.3.x is broken, not 3.4. however, your gcc 3.3.x might have been broken by compiling glibc with gcc 3.4... you see, only glibc 2.3.3_20040420-r1 has a fix for gcc 3.4 mis-handling stack smashing protection. so once glibc is without SSP, gcc 3.3.x will use __guard@GCC_3.0 instead of __guard@GLIBC_2.3.2.

:-/

Comment 4 Travis Tilley (RETIRED) gentoo-dev

2004-05-19 22:11:46 UTC

hey pappy, believe me now?

Comment 5 Tuan Van (RETIRED) gentoo-dev

2004-05-20 10:31:20 UTC

I'd like to add that after rollback to previous snapshot (vmware) and emerge gcc-3.4.0-r4, I don't have any problem yet. Note that I didn't upgrade glibc to 2.3.3_20040420-r1 and I still have gcc-3.3.3 installed.

Comment 6 merwan kashouty 2004-05-26 09:21:27 UTC

ok i am experiencing this too... so what is the correct way to avoid it if there is one.... emerge glibc-2.3.3_pre200420-r1 with gcc-3.3.3-r5 then emerge gcc-3.4.0-r4 , after which build glibc over again with the newer gcc?

i'm confused... can ya tell    :/

Comment 7 Travis Tilley (RETIRED) gentoo-dev

2004-06-05 12:57:15 UTC

this bug should be fixed as of glibc 2.3.3_pre20040420-r1. all later releases should work out of the box.