site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Hi all. Hopefully this is the right list to report this problem. To debug our SW, we try to use libgmalloc, as described here: http://developer.apple.com/technotes/tn2004/tn2124.html However we encountered troubles with libgmalloc. The following simple program is good enough to demonstrate it. [ ... ] $ gcc -O2 -fomit-frame-pointer problem.c $ DYLD_INSERT_LIBRARIES=/usr/lib/libgmalloc.dylib ./a.out foo bar Allocations will be placed on word (4 byte) boundaries. - Small buffer overruns may not be noticed. - Applications using AltiVec instructions may fail. GuardMalloc-11 Segmentation fault (core dumped) -- Terry _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... On Nov 1, 2007, at 5:16 AM, Martin Mitas wrote: GNU Malloc's alignment boundaries are insufficiently stringent for floating pint register spills, which happen when autovectorization happens (which is enable in the compiler by default), or when explicitly using floating point. This email sent to site_archiver@lists.apple.com