glibc-2.4 __stack_chk_guard/__pointer_chk_guard
Roland McGrath
roland@redhat.com
Tue Mar 7 09:47:00 GMT 2006
There is indeed no present problem. The linker behavior does the right
thing implicitly. That right thing is a potential gotcha for accidental
changes in the future. i.e., if you do introduce the symbol in the future
on some configuration, then you need to make sure that it gets into a newer
version set so that configuration's ABI version dependencies work right.
But uglifying the sources further to avoid the symbol appearing in the
version script is no less error-prone. Instead, we rely on checking the
resultant dynamic symbol lists to watch out for such stray symbols.
More information about the Libc-alpha
mailing list