On 05/13/2013 02:46 PM, David Aldrich wrote:
It is odd that this changed behaviour is associated with moving from gcc 4.1 to gcc 4.4.
It's far more likely that it's caused by the glibc version changed also part of your system upgrade.
Please can anyone suggest a fix for this problem?
You'll probably have to provide a fully contained test case to the glibc authors.
-- Florian Weimer / Red Hat Product Security Team
