Crash with LD_BIND_NOW in libm - during relocation of ifuncs
Andreas Jaeger
aj@suse.com
Mon Mar 26 13:51:00 GMT 2012
The openSUSE glibc 2.15 with a backport of the changes for avx, crashes for
a few folks during relocation of e.g. the tan function in libm - which is a
multi-arch function. This is on LInux/x86-64.
It happens during starting of KDE which uses LD_BIND_NOW=true for startup.
Removing the LD_BIND_NOW fixes the problem - as well as building glibc with
--disable-multi-arch.
https://bugzilla.novell.com/show_bug.cgi?id=753251
It crashed on an Injtel CPU with
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
lm
constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64
monitor
ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm dts
It worked for the same person on an Intel CPU with:
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp
lm
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc
aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm
sse4_1 sse4_2 popcnt lahf_lm ida dts tpr_shadow vnmi flexpriority ept vpid
I cannot reproduce it on any of my machines and thus ask whether anybody
else is aware of similar reports with LD_BIND_NOW or even a way to
reproduce it.
Thanks for any help,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
More information about the Libc-alpha
mailing list