-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Temlakos wrote: > I filed a report to Bugzilla.Ximian.com, and they said (a) "it's the > same thing we've seen before," and (b) "it's not our fault; there's some > memory corruption going on somewhere." They mentioned the "libc" file at > some point in their correspondence on this issue. Memory corruptions are highly unlikely _caused_ by glibc. The malloc functions will easily crash due to memory corruption but this does not mean there is a bug in glibc. Every glibc change has the potential to bring out new bugs; if objects are laid out differently in memory, buffer overruns will affect different regions and the newly written to ones might be more sensitive. You'll have to determine what these vague statements you got really mean. - -- â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFBlE942ijCOnn/RHQRAtKFAKCAe/S2Pt7ENLXLIGk5PuzJ6t1qiwCfQfB6 pjLHWwxUe6qlaNP0n+EaZKw= =F7fh -----END PGP SIGNATURE-----
