site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Naturally, it looks like I jumped the gun. I only had one more recursive call that had to be changed. Looks like it's working now. Still, it would be nice to know if there is anything besides a stack overflow that would cause an MCE from code. Thanks again, ...Duane --- At Tue, 24 Jul 2007 11:24:20 -0700, Duane Murphy wrote:
Howdy kernel folk, I'm working on a kext and have managed to code myself into causing a Machine Check Exception. Fun. :-)
Stack traces are meaningless so I am trying to work out the possible causes of an MCE from my code.
I'm pretty certain at one cause of an MCE is stack overflow. That's the first place I am looking. I have some code that is likely accidentally being called endlessly recursively (oops :-). (I fully understand the recursive problem, it's just a matter of finding the offending callers.)
What are the other potential causes of an MCE?
(Note: this is _not_ a hardware problem. My code is clearly causing the problem.)
Thanks for the tips,
...Duane _______________________________________________ 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... This email sent to site_archiver@lists.apple.com