site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On Dec 22, 2004, at 1:12 PM, Andrew Gallatin wrote: Thanks for the details, but I'm not very familiar with the ppc architecture. What's a common programming error that can result in this behaviour on ppc? Could returning from a function after it clobbers the stack result in this behaviour? If so, are there any "red-zone" options in the Darwin kernel that could catch something like this? William Kucharski kucharsk@mac.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... If your programmers are using assembly, inspection of their code can help find this sort of thing, and it's usually a typo (e.g. "Oh, I meant to clear %r10, not %r1...") If they're using C, overwriting the stack could easily cause this (say going beyond the bounds of an automatic array or variable.) I'm not aware of any kernel stack redzone features right off-hand, but that doesn't mean they're not there, and I'll defer to the experts on this one. This email sent to site_archiver@lists.apple.com