Re:Re:Re: How to contitnule this kind of kernel debug -----Does large memory affects?
Re:Re:Re: How to contitnule this kind of kernel debug -----Does large memory affects?
- Subject: Re:Re:Re: How to contitnule this kind of kernel debug -----Does large memory affects?
- From: searockcliff <email@hidden>
- Date: Tue, 10 Feb 2009 10:53:18 +0800 (CST)
Now the bug is found and fixed.
One function has some local variable, which does not allocate enough memory, another sub function may copy more data to the local varaible and then damaged the function stack.
It is wierd that it only panics on Mac Pro with large memory.
在2009-01-19，searockcliff <email@hidden> 写道：
Do you mean this is a bug of the kernel of Mac OS X?
Do you have some links?
在2009-01-19，"Michael Smith" <email@hidden> 写道：
>
>On Jan 18, 2009, at 7:28 PM, searockcliff wrote:
>
>> I find the line of code near the panic is memcpy().
>> But the parameters are fine.
>>
>> One important thing:
>> The kernel panic only occurs on Mac Pro with memory larger than 2GB,
>> like 3GB, 4GB,9GB and so on.
>> If I reduce the memory used to 2GB by boot-args, the kernel panic
>> disappears.
>>
>> So my question is:
>> Can the Mac OS X kernel NOT handle large memory (>2GB) well?
>
>Ask yourself this simple question:
>
>Of all the folks writing code for MacOS X, are you *really* the only
>one that has discovered this mysterious flaw?
>
>> Or the memcpy() function fails sometime on large memory?
>
>See above.
>
> = Mike
>
《大话西游外传》贺岁新作，送豪宅、送你5000元压岁钱
免费送你钻戒作情人节礼物
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden